Support Python 3 Only
See original GitHub issueAt the start of next year (2018) Django 2.0 will be released and Python 2.7 support will be a thing of the past. I want to begin the move sooner, rather than later, to a Python 3-only project.
TODO list:
- Tag the last version of this project supporting 2.7
- Remove all file encodings (
# -*- coding: utf-8 -*-
) - Remove Cookiecutter logic branches that support Python 2.7 (i.e use_python3 == ‘N’ )
- Remove any references to the
six
library - Remove all
__future__
code
As for which Python 3 version we support, for now, we’ll stick with Python 3.5. Once a few lingering issues are resolved though, I want to move us up to Python 3.6.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
What is the standard way to recommend "Python 3 only ...
If your project only runs on certain Python versions, setting the python_requires argument to the appropriate PEP 440 version specifier string ...
Read more >Porting Python 2 Code to Python 3 — Python 3.11.1 ...
A key point about supporting Python 2 & 3 simultaneously is that you can start today! Even if your dependencies are not supporting...
Read more >Cheat Sheet: Writing Python 2-3 compatible code
Python 3 only class FileDatabase: def __init__(self, filename): try: ... Python 2 only bigint = 1L # Python 2 and 3 from builtins...
Read more >Sunsetting Python 2 support
Almost all major open source Python packages now support both Python 3.x and Python 2.7, and many projects have been supporting these two...
Read more >Python 3 Installation & Setup Guide
Note that the where.exe command will work only if Python has been installed for your user account. What Your Options Are. As mentioned...
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
@jayfk I want to do this before we get Django 1.11 working. For no other reason that it’s a LTS version and I don’t want to have to support Python 2.7 for several years while people work off old commits of this project. Therefore, I’m commencing on this RIGHT NOW. 😀
Closing this as done!