7 Mar
2016
7 Mar
'16
10:07 a.m.
On Mon, Mar 7, 2016, at 11:54, Chris Angelico wrote:
It'd be a backward-incompatible change, so it would need to be explicitly invoked. Something like:
python3 -p somefile.py
which would pretend to create an __init__.py in the current directory, change to the parent, and "from dirname import somefile".
"#!/usr/bin/env python3 -p" won't work on many systems. So I think it'd be better as a magic statement within the file (possibly simply a future-import, with the possibility of eventually making it the default behavior), rather than a command-line argument.