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
Future support for Python 2 - poll #1014
Comments
Get rid of it! Although obviously, if there ends up being a 5.0.1, or 5.1.0 - they should still keep it. |
Yes, if we have to make patch/bugfix releases within 5.x, they will keep Py2(+3.4) but this are only releases we are being forced to make to ensure the 5.x series works, not 6.x releases - where we want to be - that will include new features. Would be great to kill Py2(+3.4) to speed up 6.x with Py3.5+ only. |
👍
… On 18 Apr 2020, at 15:14, Nicholas Car ***@***.***> wrote:
rdflib 5.0.0 <https://github.com/RDFLib/rdflib/releases/tag/5.0.0> has been proposed <https://github.com/RDFLib/rdflib/wiki/2020-04-03-Maintainers-Meeting-Minutes#what-do-we-want-to-tell-people> as the last rdflib release to support Python 2 (and 3.4) due to the maintenance overhead of supporting multiple versions and legacy tie-ins that prevent features of Python 3.5+ being utilised.
We would like to find out if there is strong interest in the rdflib development community in supporting Python 2 (and 3.4) going forward.
Do you agree with dropping support for Python 2 in future rdflib releases?
Indicate agreement with thumbs up reaction to this, disagreement with thumbs down. If you disagree, please add a comment to this Issue indicating why.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#1014>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHI5ECMNTH5FYW4FRFTOGLRNEZKJANCNFSM4MLGWNTA>.
|
@nicholascar - just a note that as i redploy rdflib 5.0 through conda-forge, it won't even build a 2.7 version. since 2.x has sunset in the python world. |
👍 |
Yes, only support for Python 3.x is fine. |
👍 |
1 similar comment
👍 |
Doesn't look like there's anybody speaking up for Python 2, but to flog a dead horse, the maintenance burden of supporting it is only going to get worse as the ecosystem moves on. I maintain a bug-fix-only series of a project to support Python 2.7 through the end of the year. For those releases, I've had to put maximum versions on my dependencies as APIs complete deprecation cycles in Python 3-only versions and start breaking the CI tests otherwise. I would suggest being pretty drastic and keeping Python 2 support (so your 5.x series) to an absolute minimum of bug fixes, and move A couple additional suggestions, from looking at your
|
@effigies thanks for the Yes, keeping 5.x to bug fixes and moving |
Closes: RDFLib#1014 Signed-off-by: t0b3 <thomas.bettler@gmail.com>
rdflib 5.0.0 has been proposed as the last rdflib release to support Python 2 (and 3.4) due to the maintenance overhead of supporting multiple versions and legacy tie-ins that prevent features of Python 3.5+ being utilised.
We would like to find out if there is strong interest in the rdflib development community in supporting Python 2 (and 3.4) going forward.
Do you agree with dropping support for Python 2 (and 3.4) in future rdflib releases?
Indicate agreement with thumbs up reaction to this, disagreement with thumbs down. If you disagree, please add a comment to this Issue indicating why.
The text was updated successfully, but these errors were encountered: