Dan Michael O. Heggø

Good, thanks for testing! Did you notice if it was more or less 24 hours after the start? Not too surprisining if the tokens don't last forever, but I haven't...

Hm, that's odd, I thought the login token was introduced in MW 1.24.0. Do you know if it's working in later versions in the 1.24 line? Never mind, it was...

I've been thinking about this as well. I don't think the release notes from the Github release pages are available outside Github, and that's been my reason for keeping `RELEASE-NOTES.md`...

Great!

Didn't bother copying everything into RELEASE-NOTES-md yet in case we just remove the file: https://github.com/mwclient/mwclient/commit/48b7d05f190ac8e0ca7f58497ee17166ce7b4042 Guess we just need to copy over the oldest entries.

I'm ok with keeping the file, but I won't promise that I always remember to update it. We can aim for eventual consistency :)

For what it's worth, I agree that the parameter name is quite confusing! Wouldn't really mind changing it to `chunk_size`, except it's a breaking change, so the old parameter name...

Absolutely agree that iterators should be the standard. This would just be a convenience method, to use when requesting a small number of results, which I think is quite a...

Interesting, I have actually never noticed the `max_items` parameter before :D I'm open to the idea of exposing that on the various list methods. It's not ideal, but as you...

Hm, the thing is,`site_init()` makes an API query call for 'userinfo' right away: https://github.com/mwclient/mwclient/blob/114b46c3370c202ce9abc2150406433c70cb7107/mwclient/client.py#L145 Which leads to `handle_api_response()` being called. If you are really logged in, `self.logged_in` should therefore be...