Python 2 support
See original GitHub issueUsing 2.7.15. My gut tells me this lib is python3 only but then I wonder why pip was able to install it in my python 2 env.
File "lib/python2.7/site-packages/stackprinter/__init__.py", line 163
print(format(thing, **kwargs), file=file)
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Sunsetting Python 2
As of January 1st, 2020 no new bug reports, fixes, or changes will be made to Python 2, and Python 2 is no...
Read more >Extended Support Past Python 2 EOL - ActiveState
Python 2 Extended Support ... ActiveState's extended support subscription helps you better manage your risks and secure your Python supply chain, providing:.
Read more >Sunsetting Python 2 support
The developers of the Python language extended support of Python 2.7 from 2015 to January 1, 2020, recognising that many people were still...
Read more >How to Secure Python 2 Past End of Life (EOL) with ActiveState
Answer: Official support and maintenance for Python 2 ended on January 1, 2020. The Python Software Foundation no longer offers bug fixes and ......
Read more >How is Python 2 supported in RHEL after 2020?
The PSF have announced that their "official" support of version 2 of the Python language ends on January 1st 2020 as described at:....
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
@unformatt After careful deliberation / procrastination, I think I don’t want to maintain Python 2 support myself. I’ll keep this issue open so people who need it can discover your Py 2 fork
Here is the perspective of someone who tried to get this working with Python 2 and failed:
I believe it’s important enough to explicitly state in the README that this is a Python 3 only package, since the README is the first piece of info that a new user gets exposed to. While Python 2 is going to become less and less relevant really soon, it’ll be a while till I (and probably some others) will stop instinctively think that if the README of a Python package doesn’t explicitly state supported Python versions, then it works with both 2 and 3. In my case I have installed stackprinter through pip, tried to use it in a Python 2 codebase, got it failing and only then checked setup.py, which explicitly states that this is Python 3 only.
As for the fork with Python 2 support, explicitly mentioning it in the README would probably be nice too. And how do I install it? Just
? I am noticing that setup.py of the fork still claims Python 3 only is supported, so I suppose that has to be changed too? But I’d be happy to continue the talk about the fork in an issue linked to the fork, not here.