Skip to content
This repository has been archived by the owner on Jun 9, 2020. It is now read-only.

Explicitly check for Python 3 for deciding on builtins import #12

Closed
rkern opened this issue Dec 10, 2014 · 2 comments · Fixed by #25
Closed

Explicitly check for Python 3 for deciding on builtins import #12

rkern opened this issue Dec 10, 2014 · 2 comments · Fixed by #25
Labels

Comments

@rkern
Copy link
Owner

rkern commented Dec 10, 2014

The future package provides a builtins module that masquerades as a Python 3 builtins module, but it is a read-only namespace. Injecting into it doesn't affect the actual __builtin__ namespace.

@rkern rkern added the bug label Dec 10, 2014
@rockymeza
Copy link

perhaps the try/except block could be reversed to have the Python 2 __builtin__ import first?

@altarmobile
Copy link

the future d 0.14.3 was installed. it is anaconda 2.7, and the package is running on Mac OS X 10.10.3

moreover, if I remove '@Profile' line
in ipython,

%load_ext line_profiler

from primes import primes

it runs fine

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants