[issue21062] Evalute all import-related modules for best practices

Brett Cannon added the comment: No need to keep this issue open as cleaning this stuff up will just come over time or never happen. :) -- resolution: -> works for me status: open -> closed ___ Python tracker

[issue21062] Evalute all import-related modules for best practices

Changes by Eric Snow : -- nosy: +superluser ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue21062] Evalute all import-related modules for best practices

Changes by Raúl Cumplido : -- nosy: +raulcd ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue21062] Evalute all import-related modules for best practices

Changes by Brett Cannon : -- assignee: -> brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue21062] Evalute all import-related modules for best practices

Mark Lawrence added the comment: Just a gentle reminder as it refers to zipimport and a patch was committed just a few days ago. -- nosy: +BreamoreBoy ___ Python tracker ___ ___

[issue21062] Evalute all import-related modules for best practices

New submission from Brett Cannon: I'm thinking of: * pkgutil * py_compile * compileall * modulefinder * freeze Should make sure they are (a) doing the right/best thing in the face of importlib/PEP 302/PEP 420/PEP 451, and (b) if they should be integrated into importlib somehow in a non-compat