Autoreload extension doesn't work with Python 3.2 #846

Closed
takluyver opened this Issue Oct 8, 2011 · 1 comment

Projects

None yet

1 participant

@takluyver
Member

The autoreload extension assumes that mod.py and mod.pyc files will exist in the same directory, but this is not true as of Python 3.2. See the details here:

http://docs.python.org/py3k/whatsnew/3.2.html#pep-3147-pyc-repository-directories

It should be simple to use the new APIs, but it will need a little care to ensure it works under the old system as well.

@takluyver takluyver added a commit to takluyver/ipython that referenced this issue Jan 18, 2012
@takluyver takluyver Make autoreload extension work on Python 3.
Some changes for Python 3 in general, and some changes for the .pyc repository
directories introduced in Python 3.2 (PEP 3147)

Closes gh-846
8a8884b
@minrk minrk added a commit to minrk/ipython that referenced this issue Jan 28, 2012
@takluyver @minrk takluyver + minrk Make autoreload extension work on Python 3.
Some changes for Python 3 in general, and some changes for the .pyc repository
directories introduced in Python 3.2 (PEP 3147)

Closes gh-846
a17e242
@takluyver
Member

The PR for this was merged, so I'm closing the issue.

@takluyver takluyver closed this Feb 17, 2012
@yarikoptic yarikoptic pushed a commit to yarikoptic/ipython that referenced this issue May 2, 2014
@takluyver @minrk takluyver + minrk Make autoreload extension work on Python 3.
Some changes for Python 3 in general, and some changes for the .pyc repository
directories introduced in Python 3.2 (PEP 3147)

Closes gh-846
e227a45
@mattvonrocketstein mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
@takluyver takluyver Make autoreload extension work on Python 3.
Some changes for Python 3 in general, and some changes for the .pyc repository
directories introduced in Python 3.2 (PEP 3147)

Closes gh-846
47f2a25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment