Python 3.14 support #2566
Python 3.14 support #2566
Conversation
|
Perhaps it's time to drop support for 3.8 and 3.9? 
|
|
Last year (#2398) we had to wait until October 16th 🙏🤞. |
|
Checking this out now. I do agree we should drop 3.8 and make it known that the next release will be the last for 3.9! |
|
@bmrv911 @hoffstadt |
Python 3.8 version is no longer maintained.
Python 3.8 version is no longer maintained.
|
So, I guess that might work. |
|
Awesome! 🔥🥳 |
1 similar comment
|
I hope that @hoffstadt is alive and well. Perhaps he simply went on vacation. |
I bet it's more like he is super busy 😅. It's not easy to find spare time between work and family, especially with little kids. |
|
Jonathan said he will drop the next release by the end of this week. Just be patient, I'm sure that the new release will be amazing. |
|
While we're waiting, I'd like to gather some feedback - out of sheer curiousity! - on why you guys think it's time to drop support for Py 3.8. In your opinion, what value will it bring to remove 3.8 from the list? |
The fewer versions you support, the simpler it is. And the more freedom you have in choosing tools. Otherwise, you have to restrict yourself so that it works even on outdated Python versions. If the library started using Python 3.12, it would be easy to significantly improve the type hinting. In general, we need to understand why we should support ancient versions. Are there really that many projects dependent on this library that use outdated Python and can't upgrade to at least 3.12, even though it's already time to switch to 3.13? |
|
Ouch.. forgot to add to my question: what value will it bring, considering that DearPyGui is in maintenance-only mode and is not an actively developed product 😅 |
So you mean that it would be wrong to start new projects on the latest Python version using DPG right now? Should we abandon DPG in favor of a rapidly developing alternative? Answering the clarified question: OK, if DPG is not actively developed, then the new features of the newer Python versions will probably be of little use. Therefore, I think it's probably not necessary to specifically remove support for older Python versions, but I think it can be done easily if support for older versions suddenly becomes burdensome. For example, if something from the newer versions of the language is needed. |
Absolutely not. People are still using DPG, in many scenarios it "just works", and newer Python versions do not make DPG itself "outdated" per se.
It really depends on whether DPG provides you with all you need. If not, then you might be better off using an alternative - like DearCyGui or something completely different. DPG is pretty functional and stable, and is sufficient for many projects. Also, it's not completely dead, we might be adding new things now and then (I myself have a couple of upcoming changes of this kind), it's just that the focus is on maintenance.
Totally agree. We'll get rid of old versions as soon as it becomes a burden. |
|
Hi - this was closed since it "ripped out" python 3.8. But we still want 3.14 support! |
Sorry i can see that support was added into master. Just awaiting release :) |
Yes! @bmrv911 said that Jonathan said the release would be by the end of this week. It seems to me that this week is already over. And I'm also really looking forward to the release. |
C'mon guys, it's still Sunday here 😂 (in some countries, the week starts on Monday 😉) |
|
For those that can't wait, you can temporarily link to the pypi test instance. That's what I'm doing since I don't want to downgrade my project :) |
|
Try with this: |
|
🙏🙏🙏 
|
|
😨 |
|
😔😔😔 |
5 participants
name: Pull Request
about: Python 3.14 support
title: 'Python 3.14 support'
assignees: @hoffstadt
Description:
This possible code can work for all Python 3.14 versions.