Message295298
If only someone had access to the time machine keys to fix this 20 year ago :-(. Anything beyond that last option (recognising that the script tries to import itself under another name) is bound to run into odd issues or backward compatibility concerns.
Just recognising a reimport of __main__ should avoid a lot of confusion though, from what I've seen in discussions most cases of unintentional shadowing of the stdlib is caused by folks naming a exploratory script the same as a stdlib module (e.g. naming a script "socket.py" when experimenting with sockets).
W.r.t. "from . import ..." and scripts: installing using entry points isn't a problem, but installing using plain distutils still is as is the even more low-tech option of just copying files to the right location (maybe using a Makefile). But that issue is moot now that Guido has stated he doesn't like the idea. |
|
Date |
User |
Action |
Args |
2017-06-06 19:54:51 | ronaldoussoren | set | recipients:
+ ronaldoussoren, barry, ncoghlan, Rosuav |
2017-06-06 19:54:51 | ronaldoussoren | set | messageid: <1496778891.58.0.0977863372267.issue29929@psf.upfronthosting.co.za> |
2017-06-06 19:54:51 | ronaldoussoren | link | issue29929 messages |
2017-06-06 19:54:51 | ronaldoussoren | create | |
|