Adam Williamson
Adam Williamson
I'd say we de facto have "long-term stability of usage" - anyone using mwclient now has to be pretty used to how it works at present =) I guess I...
I'm gonna suggest we go ahead and do a 1.0 release with more or less what we have now (we will need to come up with a new way of...
Similarly on the async stuff, I don't think it should hold up doing a 1.x release *now*. I think we can definitely look at it, though. I'll file a separate...
Heads up on this for other maintainers @waldyrious @btongminh @marcfrederick - I've finally got a bit of spare time and am trying to set up a release workflow now following...
https://github.com/mwclient/mwclient/pull/331 adds a release workflow.
OK, I just tested the release workflow using testpypi and a test repo - https://github.com/AdamWill/mwclient-test , https://test.pypi.org/manage/project/mwclient/releases/ . as you can see, it seems to work fine. So, I propose...
oh, no, I don't believe we did anything about that. I haven't looked at it in detail but your proposal sounds sensible, do you want to send a PR?
Looking at the milestone, there's also https://github.com/mwclient/mwclient/issues/197 .
let's discuss it over in that issue.
@RheingoldRiver you mean https://github.com/mwclient/mwclient/issues/259 ? Hmm...maybe we can just add a deprecation warning to `limit` saying its replacement will be determined in future? Or just the "rename it to `chunk_size`...