Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish an update to match the documentation #330

Closed
azurstarshine opened this issue Apr 25, 2024 · 2 comments
Closed

Publish an update to match the documentation #330

azurstarshine opened this issue Apr 25, 2024 · 2 comments

Comments

@azurstarshine
Copy link

azurstarshine commented Apr 25, 2024

I'm getting the following warning:

WARNING:mwclient.client:Subscribe to the mediawiki-api-announce mailing list at https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/ for notice of API deprecations and breaking changes.
WARNING:mwclient.client:Main-account login via "action=login" is deprecated and may stop working without warning. To continue login with "action=login", see [[Special:BotPasswords]]. To safely continue using main-account login, see "action=clientlogin".

That led me to the documentation that Site.login is deprecated in favor of Site.clientlogin. All well and good, but Site.clientlogin does not exist in the most recently published version from 2020.

This is confusing as a user of the library and makes the project look dead/abandoned. I suggest publishing an update to both the library and the documentation in the very near future (maybe within a month) to show that it is not dead and to avoid this sort of confusion. It's been 3 years since a release. That is very concerning if I want to depend on this library's continued stability, and I very much do. The official alternative, pywikibot, is a convoluted nightmare of object obsession and required on-disk configuration and wastes enormous amounts of time trying to figure out how it's supposed to work. This library is simple, clear cut, and has a much more Pythonic design. The release doesn't need to be 1.0. It can be 0.11. I'd just like to see some kind of release and consistency between the latest release and the docs.

@AdamWill
Copy link
Member

AdamWill commented Apr 25, 2024

We are already planning a new release. Filing a long issue with a hectoring tone is not helping. This project is maintained by volunteers in our spare time, we all have day jobs and nobody is getting paid. When I'm not sitting here doing my day job at 10pm I'll try and get the release finished up. Thank you.

edit: in case it wasn't clear, the original maintainer of the project went inactive, and there was no real maintenance for a while. Last year Marc, myself and a few others picked up the maintenance of the project and we are working towards a new release, but there has been a lot of work involved. We had to work through the backlog of issues and PRs. We had to build a modern CI flow (the project was still attempting to use travis for CI). We had to get access to the pypi project, which took a while. The last remaining piece is to build a modern release workflow; AFAICT previously Dan just handled releases manually, the project has no release script or automated release process. I intend to build a proper release workflow via Github Actions, but I need a bit of clear time to do that, and I haven't had it.

We are working on this, please be patient.

@AdamWill
Copy link
Member

AdamWill commented May 4, 2024

This is effectively a dupe of #284 . as mentioned there I am working on a release workflow now.

@AdamWill AdamWill closed this as not planned Won't fix, can't repro, duplicate, stale May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants