-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
New release on Pypi #1635
Comments
Hi, I second this request. The latest release has a lot of warnings that were fixed in git like |
Yeah, looks like that was fixed 49b74ca, just a couple days after 4.2.5 was released to PyPI. |
Theres been some CPU fixes too, 2a93d6b What would be needed to get a 4.3.0 or a 4.2.6 release on pypi? |
Perhaps a concrete action here would be to create a PR for pypi release from GitHub actions to reduce the manual load on the maintainers. That way a tag can create a release (at least a dev one on test.pypi). |
It has been almost two years of commits since 4.2.5. Not sure if I need them but I only like to use projects that are relatively up to date and active. This project is active but the release is out of date. I assume there is something like a stable release in these commits somewhere. Not really knowing which commit I decided to just clone the latest commit and run that to see assumming all the commits are vetted/tested. On alpine (in docker container image) I did this. first install the supervisor package
If the maintainers ask for some help maybe we can assist with clearing/closing all the old issues and assuming this repo is not just a mirror making a CI for a stable/dev releases. I figure the alpine package generator is only waiting on a new stable tag/release and then we would see the new version in the package so that's why it's so stale at this point. |
Hello, could you do a new release on pypi ? It's been more than a year now and there have been several bugfixes included in main branch since then.
Thanks.
Thomas.
The text was updated successfully, but these errors were encountered: