Julien Danjou wrote:
On Tue, Nov 24 2015, Eric Kao wrote:
I¹ve been using the python-future library for Python 3 porting and want to
see what people think of it. http://python-future.org/overview.html#features
The end result is standard Python3 code made compatible with Python2 through
library imports. The great thing is that Python 3 execution is mostly
independent of the library, so once Python 2 support is dropped, the use of
the library can be dropped too.
Anyone know why it¹s not used in OpenStack perhaps alongside six? Thanks!
python-future has been a dependency of pytimeparse¹ for a while and it
has been a nightmare. IIRC, python-future blends into Python magically
so it is somehow automatically imported each time you run Python. This
had a tendency to break random other Python packages installed in the
environment.
Oh, please no then, magically messing with other python packages by
monkeying with the internals of python we already have enough of (cough
cough eventlet, cough cough parts of jsonutils in oslo.serialization
that injects itself into anyjson)...
Just say no to more please ;)
In the end we just dropped it from pytimeparse and we're much happier.
And we're very happy with six. :)
¹ It's used by Gnocchi.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
