future: Easy, safe support for Python 3/2 compatibility
future is the missing compatibility layer between Python 3 and Python 2. It allows you to use a single, clean Python 3.x-compatible codebase to support both Python 3 and Python 2 with minimal overhead.
Notable projects that use future for Python 2/3 compatibility are Mezzanine and ObsPy.
For new code, it is designed to be used as follows:
from __future__ import (absolute_import, division,
print_function, unicode_literals)
from future.builtins import (
bytes, dict, int, list, object, range, str,
ascii, chr, hex, input, next,
oct, open, pow, round, super,
filter, map, zip)
followed by predominantly standard, idiomatic Python 3 code that then runs similarly on Python 2.6/2.7 and Python 3.3+.
The imports have no effect on Python 3. On Python 2, they shadow the corresponding builtins, which normally have different semantics on Python 3 versus 2, to provide their Python 3 semantics.
Standard library reorganization
from future import standard_library provides a context-manager called hooks that installs import hooks (PEP 3108) to allow renamed and moved standard library modules to be imported from their new Py3 locations.
Automatic conversion
An included script called futurize aids in converting code (from either Python 2 or Python 3) to code compatible with both platforms. It is similar to python-modernize but goes further in providing Python 3 compatibility through the use of the backported types and builtin functions in future.
Documentation
Credits
- Author:
Ed Schofield
- Sponsor:
Python Charmers Pty Ltd, Australia, and Python Charmers Pte Ltd, Singapore. http://pythoncharmers.com
- Others:
See docs/credits.rst or http://python-future.org/credits.html
Licensing
Copyright 2013-2014 Python Charmers Pty Ltd, Australia. The software is distributed under an MIT licence. See LICENSE.txt.
Metadata
Release files for future 0.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| future-0.12.0.tar.gz | 553.9 kB | Without provenance | Details for future-0.12.0.tar.gz |
Release files / future-0.12.0.tar.gz
| Download URL | future-0.12.0.tar.gz |
|---|---|
| Size | 553.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc49f4ccd55b289234b09bb4b4b2ab8017ce91845f7013a9b5daa3f25855794e
|
|
BLAKE2b-256 checksum How to use checksums |
02f8f284a56149af9e72da9605cb178175f4acdfedc4655aabee19a138acd6fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for future 0.12.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.