bpo-38715: Fix compileall.compile_dir() ddir regression #17398
Conversation
This fixes a regression introduced in Python 3.5 that means the ddir parameter on the compileall.compile_dir() function is no longer applied hierarchically to subdirectories but instead the source path reported in exception traces is flattened so all subdirectory information is lost. https://bugs.python.org/issue38715
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
|
Hi, I was unaware of Python's licencing requirements. I would rather completely reassign the copyright for this contribution to the PSF rather than submitting personal details for licencing. If that's not possible, please close this PR. |
|
Thank you, @hetmankp. I'll close the PR as per your request. |
4 participants
This fixes a regression introduced in Python 3.5 that means the ddir
parameter on the compileall.compile_dir() function is no longer applied
hierarchically to subdirectories but instead the source path reported in
exception traces is flattened so all subdirectory information is lost.
https://bugs.python.org/issue38715
https://bugs.python.org/issue38715