Éric Araujo mer...@netwok.org added the comment:
Please keep the discussion in one place, the other bug report.
--
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14967
New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
due to the lack of a marker that denotes where the module ends and the
attribute starts, unrelated import errors can break the tryerror chain at
unexpected places and the code can pass on to the recursive getattr chain,
Tarek Ziadé ziade.ta...@gmail.com added the comment:
the current code works as expected. Why not leaving it like this since your
change seem to be comsetics only ?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14967
Tarek Ziadé ziade.ta...@gmail.com added the comment:
can you give an example of a bad error ?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14967
___
Changes by Tarek Ziadé ziade.ta...@gmail.com:
--
resolution: - duplicate
superseder: - Improve error reporting for packaging.util.resolve_name
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14967
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
to correctly implement it we need the : separator back
with the separator the import specification is no longer ambigious,
and we can use one exact import, and an error will always be an error
--
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
an example of creating a wrong error would be something like the following:
there is a package foo.bar, which does a wrong import in __init__.py
we want to resolve the name foo.bar.something
we'd get the error that foo has no
