Roundup Robot added the comment:
New changeset 3dcc81c2eef5 by Brett Cannon in branch '3.3':
Issue #17358: imp.load_source() and load_compiled() should now return
http://hg.python.org/cpython/rev/3dcc81c2eef5
New changeset be6bbc9f0561 by Brett Cannon in branch 'default':
merge for issue #17358
Brett Cannon added the comment:
I figured out why testing was difficult; the file is only read from if it's
necessary. That means if you are trying to load source which has bytecode
available which is legitimate it will simply skip over the source and read from
the bytecode.
So in the end I
Changes by Brett Cannon br...@python.org:
--
assignee: - brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17358
___
___
Kushal Das added the comment:
Working on a patch for this.
--
nosy: +kushaldas
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17358
___
___
Kushal Das added the comment:
Can not reproduce it :(
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17358
___
___
Python-bugs-list mailing list
New submission from Brett Cannon:
As of right now, if you use imp.load_module(), it will store any 'file'
argument you give it in a hacked loader. That's a problem when you call
imp.reload() on such a module, though, as subsequent calls to
__loader__.load_module() will attempt to use the
Roumen Petrov added the comment:
How to reproduce issue with normal in source tree build ?
I'm asking because to avoid issue, on read only file system , I use patch
posted in scope of issue3754 and issue15833
(0016-CROSS-reload-may-fail-with-operation-on-closed-file-.patch) .
--
Brett Cannon added the comment:
I don't have a Python 3.3 install happy (someone at work reported the failure),
but simply calling imp.load_module() and then __loader__.load_module() on the
returned module immediately after should trigger it.
--
