-
Notifications
You must be signed in to change notification settings - Fork 45
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
Support Python 3.13 #239
Comments
Thank you for the reminder. Actually, I read yesterday that Python 3.13 was released. I plan to make new releases of my library with new features this month, both for Python and Rust. I will make sure that Python 3.13 is supported. |
Hi, id like to come back to this. I see on PyPI that there is a 2.0.2 release which supposedly supports python 3.13 ( If there is support needed to get 3.13 to work i would have a bit of time to help with that. |
@JanEricNitschke Please use Python 3.12 for now if you want to use the Rust implementation of my library. Last month, I released Lingua 1.4.0 which supports Python 3.13 and has new features. It's pure Python so it's slower than the Rust implementation. Your help is appreciated but I want to implement the new features from the pure Python implementation first before I make a new release with Python 3.13 support. So there is nothing to do for you at the moment. The wheels will be created in CI when I make the next release. My spare time is currently limited but I will make a new release. I just can't tell you when. |
@pemistahl Thanks for the quick reply. If i understood correctly then 1.X is the pure python version and 2.X the rust version, right? Unfortunately it is pretty important for us to use both the rust implementation and make python 3.13 available. Would there be an option to do like a patch release to just get 3.13 support out? |
No, I'm sorry. Each release takes a significant amount of storage space on PyPI which is limited. I won't make a new release only for Python 3.13 support. |
Could there be, by chance, an option to delete the current version supporting |
@arthur-st No, I won't do that. Removing released versions from PyPI is like a punch in the faces of people who already rely on that specific version in their projects because their builds will break. I did that in the past because of significant bug fixes and because of limited storage on PyPI. However, storage on PyPI has luckily been increased for my project so that I don't need to remove released versions anymore. I'm wondering why you need Python 3.13 so urgently in the first place. Is it because of the new free-threaded mode of operation? Otherwise, I don't see what you can accomplish with 3.13 that you cannot still accomplish with 3.12 already. |
Fair enough, appreciate the response. As to why I want 3.13 support - the first maintenance release is out, so we're starting to use it both for new projects and for maintenance upgrades. Lingua is the only package blocking 3.13 updates for multiple projects, existing and greenfield, which is going to require me to have a maintenance schedule that's specifically about Lingua. In terms of actual language features, interpreter/locals and typing improvements are more interesting to me than the free-threading. Also, just a good number of smaller improvements, like for |
Well, this is no urgent reason, isn't it? Python 3.12 will also get maintenance releases until the end of 2028. After all issues in milestone 6 and milestone 9 have been implemented, I will make a new release. Not earlier. I'm glad that my library is used in real projects. But I'm doing all of this free of charge in my spare time which has never been as limited as it is now. That's why the current progress is slow. That's not nice but I can't help it. I hope you understand. |
I do understand that, and I appreciate your effort as an OSS volunteer. That said, I would like to note that the understanding goes both ways, in that you're not necessarily the person to judge whether if our projects are being prematurely upgraded to 3.13 or not, or how our technical debt planning should look like. Meaning, that you can make your point without telling me that I should be happy with staying on 3.12 for another 3 years. |
While waiting for the release, you can compile a Python 3.13 wheel yourself and install it. Maybe this is a temporary solution for you? But you will need to install Rust first. After Rust is installed, you can do it like this:
You will then find the wheel file in folder |
I'm afraid that won't work for my current projects, but I appreciate the thought. |
No rush from me personally, but during a routine "see if my project can run in Python 3.13" (which was officially released very shortly ago), this project was one of my few dependencies that didn't have a 3.13 version available.
So this issue is a request/reminder to add a build for Python 3.13.
The text was updated successfully, but these errors were encountered: