Nick Coghlan wrote: > Fixing direct execution inside packages > --------------------------------------- > > To fix this problem, it is proposed that an additional filesystem check be > performed before proceeding with direct execution of a ``PY_SOURCE`` or > ``PY_COMPILED`` file that has been named on the command line. > > This additional check would look for an ``__init__`` file that is a peer to > the specified file with a matching extension (either ``.py``, ``.pyc`` or > ``.pyo``, depending what was passed on the command line). > > If this check fails to find anything, direct execution proceeds as usual. > > If, however, it finds something, execution is handed over to a > helper function in the ``runpy`` module that ``runpy.run_path`` also invokes > in the same circumstances. That function will walk back up the > directory hierarchy from the supplied path, looking for the first directory > that doesn't contain an ``__init__`` file. Once that directory is found, it > will be set to ``sys.path[0]``, I think you mean that sys.path[0] will be set to the directory path. Should the current working directory continue to be included in the path when running a sub-package module? -- Steven
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4