A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-August/091364.html below:

[Python-Dev] Excluding the current path from module search path?

[Python-Dev] Excluding the current path from module search path? [Python-Dev] Excluding the current path from module search path?P.J. Eby pje at telecommunity.com
Tue Aug 25 18:30:00 CEST 2009
At 04:59 PM 8/25/2009 +0100, Chris Withers wrote:
>Hi All,
>
>I'm being bitten by this issue:
>
>http://bugs.python.org/issue1734860
>
>I'm not sure I agree with Daniel's closing of it so thought I'd ask here...
>
>Am I right in thinking that the general idea is that "the current 
>working directory at the time of invoking a script or interpreter 
>ends up on the python path" or should I be thinking "the directory 
>that a script exists in should end up on the python path"?
>
>If the latter, then what happens in the case of just starting up an 
>interpreter?

It's the latter.  In the case where there is no script, then the 
current directory is considered to be the directory of the script.

More information about the Python-Dev mailing list

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