[issue9872] `a.b.my_function is not b.my_function` when `a` and `b` are both on `sys.path`

Ram Rachum cool...@cool-rr.com added the comment: Benjamin, This behavior is involved in a problem I have with Django. When using Django, you have apps that live inside a project: my_project\ __init__.py my_app\ __init__.py views.py So if you have a view function in `views.py`,

[issue9872] `a.b.my_function is not b.my_function` when `a` and `b` are both on `sys.path`

Amaury Forgeot d'Arc amaur...@gmail.com added the comment: I suggest to report this to the Django team. -- nosy: +amaury.forgeotdarc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9872 ___

[issue9872] `a.b.my_function is not b.my_function` when `a` and `b` are both on `sys.path`

New submission from Ram Rachum cool...@cool-rr.com: Let's say you have this structure: a\ __init__.py b\ __init__.py In `b.__init__` a function called `my_function` is defined. And assume that `a` and `b` are both on `sys.path`. Then this situation happens: import a.b

[issue9872] `a.b.my_function is not b.my_function` when `a` and `b` are both on `sys.path`

Benjamin Peterson benja...@python.org added the comment: And indeed that's expected. Don't do that. -- nosy: +benjamin.peterson resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9872