remove Python2 support in command_line_runner
See original GitHub issueDescription
README.md says,
Unfortunately Python 2.7 support has been discontinued 😦
I think we can drop support for the older version of Python here.
I am not sure if we still need utf-8 encoding. Maybe we can do like this?
utf8_result = howdoi(args).encode('utf-8', 'ignore')
sys.stdout.buffer.write(utf8_result)
# or
result = howdoi(args)
print(result)
Have you read the Contributing Guidelines on Pull Requests on mkdocs?
Yes
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Remove support for python2 · Issue #7198 · emscripten-core ...
MacOS has Python2 built in, but not Python3. Python2 may be removed at some point. · The emsdk ships python 2.7 for windows....
Read more >How to completely uninstall python 2.7.13 on Ubuntu 16.04
sudo apt purge python2.7-minimal.
Read more >Python 2 to 3 Quick Guide - Ji ZHANG's Blog
When dealing with non-ASCII encodings in Python 2, there're str , unicode ... basestring is removed, use str as type: isinstance(s, str) ...
Read more >How to remove Python 2 from Ubuntu 20.04?
So, it was relatively easy to uninstall python2. To uninstall, enter following commands in terminal: sudo apt remove python2 --simulate sudo apt ...
Read more >How to remove python2 from /usr/bin/.... folder
If you want to remove python2. 7, you can simply use following command, removes the python which is installed with homebrew:
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 FreeTop 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
Top GitHub Comments
@gleitz I submitted a PR #427.
I will work on
page_cache
problem in another issue!I had this problem as well! The tests seem to run properly when I open a PR, but locally when they run they throw this error.
I was wondering if somehow the
page_cache
is not being used when running the test locally. It’s almost as if it’s making the live call to StackOverflow rather than using the cache.