Chris Angelico added the comment:
If someone made a new way of importing and had it raise ValueError on some
issue or other, I think there'd be complete consensus that that's the wrong
exception. Yes, this is incompatible with Python 2 - but there are a lot of
corner cases in the 3.3+ import code that differ from 2.7. What we have is a
code error ("relative imports outside of packages don't make sense, dummy!")
and the only difference is which exception is being raised (ValueError,
SystemError, ImportError). It's not like working code has different semantics.
But even if ValueError is chosen, I would still greatly prefer that to
SystemError. When my student told me he was getting SystemError, I started
trying to diagnose a corrupted venv, not a buggy script.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue18018>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
