builtins confusion

Robin Becker robin at reportlab.com
Mon Nov 5 04:47:40 EST 2018


For some reason I find my windows 32 bit python 2.7.13 has a package called builtins installed in site-packages. This creates 
confusion about how to look at builtins.

The __init__.py looks like this


from __future__ import absolute_import
import sys
__future_module__ = True

if sys.version_info[0] < 3:
     from __builtin__ import *
     # Overwrite any old definitions with the equivalent future.builtins ones:
     from future.builtins import *
else:
     raise ImportError('This package should not be accessible on Python 3. '
                       'Either you are trying to run from the python-future src folder '
                       'or your installation of python-future is corrupted.')

this creates complete confusion about how to import __builtin__ versus builtins. I think this is associated in some way with 
pyinstaller, but am not sure.

Is this a reasonable way to import either builtins / __builtin__


try:
     import __builtin__
except ImportError:
     import builtins as __builtin__

-- 
Robin Becker




More information about the Python-list mailing list