[issue21553] Behaviour of modules depends on how they where imported

Changes by Berker Peksag : -- superseder: -> Add '-p'/'--path0' command line option to override sys.path[0] initialisation ___ Python tracker ___ __

[issue21553] Behaviour of modules depends on how they where imported

Eric Snow added the comment: This is a consequence of a script's directory getting prepended to sys.path. See issue #13475. -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker

[issue21553] Behaviour of modules depends on how they where imported

Peter Otten added the comment: Here's a simpler demo for what I believe you are experiencing: $ mkdir package $ cd package/ $ touch __ini__.py module.py $ export PYTHONPATH=.. $ python3 Python 3.3.2+ (default, Feb 28 2014, 00:52:16) [GCC 4.8.1] on linux Type "help", "copyright", "credits" or "l

[issue21553] Behaviour of modules depends on how they where imported

Changes by Ezio Melotti : -- nosy: +brett.cannon, eric.snow, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue21553] Behaviour of modules depends on how they where imported

New submission from mythsmith: I found a condition where different behaviour could be observed depending on how a module is imported. It seems to be different to write: import module # against: from package import module In the attachment you find a minimal package (imptest) with this organi