Changes by Jake Garver <j...@garverhouse.org>:
Added file: http://bugs.python.org/file41663/Python351-no-unreachable-check.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Jake Garver added the comment:
Updated patch. Same as before, but updates tests.
Sorry I went MIA on this issue.
--
Added file: http://bugs.python.org/file40440/python34_compileall_ddir_2.diff
___
Python tracker <rep...@bugs.python.org>
Jake Garver added the comment:
I agree. I couldn't find a use for the check, so I removed it entirely in the
provided patch. I'm running that way now with success, but of course I'm
covering just one use case.
Digging back a bit further, the isdir() check came in here:
https://github.com
New submission from Jake Garver:
In compileall.py's main, we verify that the provided destdir (-d) exists at
build time. But destdir will commonly be used to override the build time path
with a runtime path. That runtime path will usually not exist at build time.
Note that this logic
Jake Garver added the comment:
Thanks for the response and sorry for the mis-read.
In 2.7, I did something like:
python -m compileall -d /runtime/path foo.py
But in 3.4, I get:
-d destdir requires exactly one directory argument
I'm doing this during a build. Then we package the pyc file
