Reinstate support for python 3.5
See original GitHub issueLooks like a commit on Jan 13 removed support for python 3.5. I am trying to understand why this is no longer supported.
I was able to find below reason for python 3.4.
A segfault was found when running
redis-pyin python
3.4.0that was introduced into the codebase in python itself in the version
3.4.0.
Also, the redis-py library still supports python 3.5 and python 3.5 has not reached EOL yet.
Thanks for any additional information on this issue.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Reinstating python 3.5 support in the next version would be nice.
It looks like support was removed with only two simple commits, and those commits didn't actually make a functional change. In fact, it...
Read more >Changements — Documentation Python 3.5.10
This document is for an old version of Python that is no longer supported. You should upgrade, and read the Python documentation for...
Read more >How do I decompile Python 3.5 .pyc? - Stack Overflow
The ones I know about that handle Python 3.5 (and other Python versions) are: uncompyle6 · pycdc. [Disclamer: I develop 1].
Read more >How to Install and Manage Multiple Python Versions in WSL2
It can also restore the source code to a previous version from the entire history of the repository. Copy the command from below...
Read more >7.x Series — IPython 8.7.0 documentation
IPython 8.0 will drop support for Python 3.7, removed nose as a dependency, and 7.x will only get critical bug fixes with 8.x...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
My philosophy for supported python version in the 3.x version series is to support the latest + the 2 versions behind it. I think this is a way that most packages that is built for python3 versions should be supported and done in general. I will give it some thought tho to possible revert that as i have stated before that i want to follow the supported matrix that redis-py uses to preserv compatibility. Thanks for brining it up.
MR #358 merged, closing issue