Can I Use Python 3?
How do you tell if a project has been ported to Python 3?
On PyPI each project can specify various
(typically in a project’s
setup.py through a
There are various classifiers related to what version of Python a project can
run on. E.g.:
Programming Language :: Python :: 3 Programming Language :: Python :: 3.0 Programming Language :: Python :: 3.1 Programming Language :: Python :: 3.2 Programming Language :: Python :: 3.3 Programming Language :: Python :: 3.4
As long as a trove classifier for some version of Python 3 is specified then the
project is considered to support Python 3 (project owners: it is preferred you
at least specify
Programming Language :: Python :: 3 as that is how you
end up listed on the Python 3 Packages list on PyPI;
you can represent Python 2 support with
Programming Language :: Python).
The other way is through a manual override in
caniusepython3 itself. Projects ends up on this list because:
- They are now part of Python’s standard library in some release of Python 3
- Their Python 3 port is under a different name
- They are missing a Python 3 trove classifier but have actually been ported
If any of these various requirements are met, then a project is considered to support Python 3 and thus will be added to the manual overrides list. You can see the list of overrides when you use caniusepython3’s CLI with verbose output turned on.
What if I know of a project that should be added to the overrides file?
If a project has Python 3 support in a release on PyPI but they have not added the proper trove classifier, then either submit a pull request or file an issue with the name of the project and a link to some proof that a release available on PyPI has indeed been ported (e.g. PyPI page stating the support, tox.ini file showing tests being run against Python 3, etc.). Projects that have Python 3 support in their version control system but not yet available on PyPI will not be considered for inclusion in the overrides file.
How can I get a project ported to Python 3?
Typically projects which have not switched to Python 3 yet are waiting for:
- A dependency to be ported to Python 3
- Someone to volunteer to put in the time and effort to do the port
caniusepython3 will tell you what dependencies are blocking a project
that you depend on from being ported, you can try to port a project farther
down your dependency graph to help a more direct dependency make the transition.
Which brings up the second point: volunteering to do a port. Most projects happily accept help, they just have not done the port yet because they have not had the time (“volunteering” can also take the form of paying someone to do the port on your behalf). Some projects are simply waiting for people to ask for it, so even speaking up politely and requesting a port can get the process started.
If you are looking for help to port a project, you can always search online for various sources of help. If you want a specific starting point there are HOWTOs in the Python documentation on porting pure Python modules and extension modules.
4.0.0 [under development]
- Stop using PyPI’s XML-RPC API and move to its JSON one for better performance (and switch to https://pypi.org)
- Load the overrides data from GitHub when possible, falling back to the data included with the package when necessary (thanks to shafrom for adding local, one-day caching)
- Return a
3error code when a command completes successfully but there are found blockers (patch by pcattori)
- Fix a dict comprehension failure with the pylint checker (patch by Jeroen Oldenburger)
- Usual override updates
- Python 3.5 support
- Tests have been made less flaky
- Use pypi.io instead of pypi.python.org
- Normalize project names to help guarantee lookup success
- Made tests more robust in the face of PyPI timing out
- Added Python 3.5 support
- Dropped Python 2.6 and 3.2 support
- Updated tests to not use Twisted as a Python 2-only project
- Fixed a bug where the pylint checker was incorrectly missing
from __future__ import unicode_literals(issue #103; reported by David Euresti)
- Usual overrides updates
- Fix a failing test due to the assumed unported project being ported =)
- Work around distlib 0.2.0 bug (patch by @rawrgulmuffins)
- Usual override updates
- Log more details when running under
-v(patch by @msabramo)
- Print a