Description

assignee = None
closed_at = <Date 2006-02-17.12:13:09.000>
created_at = <Date 2006-02-01.14:48:37.000>
labels = ['interpreter-core']
title = 'IMPORT PROBLEM: Local submodule shadows global module'
updated_at = <Date 2006-02-17.12:13:09.000>
user = 'https://bugs.python.org/jensengel'

activity = <Date 2006-02-17.12:13:09.000>
actor = 'georg.brandl'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2006-02-01.14:48:37.000>
creator = 'jens_engel'
dependencies = []
files = []
hgrepos = []
issue_num = 1421513
keywords = []
message_count = 2.0
messages = ['27393', '27394']
nosy_count = 2.0
nosy_names = ['georg.brandl', 'jens_engel']
pr_nums = []
priority = 'normal'
resolution = 'postponed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1421513'
versions = []

Activity

1. jensengel commented on Feb 1, 2006

   

   jensengelmannequin

   on Feb 1, 2006

   MannequinAuthor

   More actions

   PYTHON: 2.3, 2.4
   PLATFORMS: Solaris, Linux, Cygwin, Win32

   Local sister modules seem to hide global ones (of the
   standard Python library) when import occurs in a
   submodule. This statement even holds for indirect
   imports from the standard Python library.

   FILE STRUCTURE for EXAMPLES:

   • my/
     +-- __init__.py
     +-- main.py
     +-- main2.py
     +-- symbol.py
     \-- types.py

   EXAMPLE 1: Local submodule shadows global one.
   # -- file:my.main.py
   # COMMAND-LINE: python my/main.py
   # MY INTENTION: Import standard module "types".
   import types #< FAILURE: Imports my.types

   if __name__ == "__main__":
       print types.StringTypes  #< EXCEPTION: StringTypes 
   are not known.
   # -- FILE-END

   EXAMPLE 2: Indirect import uses "my.symbol" instead.
   # -- file:my.main2.py
   # COMMAND-LINE: python my/main2.py
   # MY INTENTION: Import standard module "compiler".
   # NOTE: Module "compiler" imports module "symbol"
   import compiler #< FAILURE: Imports my.symbol instead

   if __name__ == "__main__":
       pass
   # -- FILE-END
     
   NOTE: Module import problems can be better checked 
   with "python -v".

   I have not found a work-around that let me decide if I
   want to import the global module or the local one. The
   only solution seens to be to relocate the module
   where "__main__" is used to another place where no
   such import conflict occurs.

   If my analysis is correct, the "main" module provides
   another ROOT filesystem for Python libraries that is
   normally preferred over the PYTHONHOME filesystem.
   If this is true, module names at this level must be
   UNIQUE in a GLOBAL namespace (that is only partly
   under my control) which I consider BAD.

   NOTE: In C++ if have the "::" prefix to indicate that
   I want to use the global/default namespace (=module)
   and not a sub-namespace. I am not aware of such a idom
   in Python.
2. jensengel

   closed this as completedon Feb 1, 2006
3. jensengel

   added

   interpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)

   on Feb 1, 2006
4. jensengel

   closed this as completedon Feb 1, 2006
5. jensengel

   added

   interpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)

   on Feb 1, 2006
6. birkenfeld commented on Feb 17, 2006

   

   birkenfeld

   on Feb 17, 2006

   Member

   More actions

   Logged In: YES
   user_id=1188172

   This is, unfortunately, correct behavior. Python 2.5 will
   hopefully fix this with new import semantics for relative
   imports.

   As a workaround, don't call your modules like global ones
   when you need those.
7. ezio-melotti

   transferred this issue fromon Apr 10, 2022

Issue actions