-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Tracking: need for a new release #212
Comments
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a lot of fixes to existing issues that aren't on PyPI because there hasn't been a release in a long time.
I am thinking I want to clean up and finish all the actionable issues, do a test of all functionality on latest versions, maybe write new tests if anything is broken, and then push out a new release. There are also some outstanding documentation issues that need to be taken care of.
The Python version bump to 3.10 is considerable and is part of the reason releases have been stalled for a while. 3.10+ is available in Ubuntu LTS (jammy), Debian stable (bookworm), Raspbian stable (bookworm), and Anaconda's mainline, which are my usual yardsticks of whether it's acceptable to bump. I don't imagine there won't be a bit of pushback, but I think the version has been out for long enough.
Python 3.12 is only about a month away, so I might hold on until right after its release, but the related cleanup work should be done before then.
The text was updated successfully, but these errors were encountered: