aklajnert <pyt...@aklajnert.pl> added the comment:
I agree that adding a package directory to PYTHONPATH is not a good idea, however, I've stumbled on it in two completely independent companies' codebases. So it makes me suspect that this is may not be that rare case. In the previous company we got bitten by this problem, and debugging took quite some time as this issue usually doesn't reveal immediately. If the relative path is resolved to the same module as not relative, then the behavior when the same file's path but referenced in a slightly different way isn't seems at least inconsistent. Note that the absolute path to the module is exactly the same, the only thing that is different is how you reference it. I'm happy to make an attempt to fix it if it gets acknowledged as a bug (a little guidance would be also helpful). ---------- status: pending -> open _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46806> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
