On Thu, 14 Oct 2004, Phillip J. Eby wrote: > Perhaps this means that -m is premature? I personally would rather wait > for 2.5 if it means we get a nice, future-proof "main" convention out of > the deal. While -m would not then be "backward compatible" with existing > scripts, people could start changing scripts to match the convention as > soon as there was an accepted PEP. But to me -m option and __main__() conventions seem like orthogonal features... Even if current __name__=="__main__" blocks get replaced by a magic __main__() function, you would still benefit from -m cmd line option Or is there some hidden dependency? Ilya > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/ilya%40bluefir.net >
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4