[issue27012] Rename the posix module to _os

2016-05-26 Thread ppperry
Changes by ppperry : -- versions: +Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue27012] Rename the posix module to _os

2016-05-12 Thread Brett Cannon
Brett Cannon added the comment: You're correct that it could break code checking the module's __name__ value if that was changed. As for why I care, it sucks trying to import this module for any reason. Any place you touch this module you have to proper try/except ImportError checks to work a

[issue27012] Rename the posix module to _os

2016-05-12 Thread R. David Murray
R. David Murray added the comment: I know you know this, but to be clear for other readers, the module naming happens at compile time, not runtime. If you alias the module, it's __name__ will still be '_os', won't it? Might that not have backward compatibility issues? And if you also change

[issue27012] Rename the posix module to _os

2016-05-12 Thread Brett Cannon
New submission from Brett Cannon: It's always bugged me that the posix module changes its name based on what OS you're running under. I think it would be better to name the module _os as that it's consistent. We can alias the name to posix/nt for backwards compatibility (and even do this in im