[Python-Dev] PEP 328 and PEP 338, redux
Guido van Rossum
guido at python.org
Thu Jun 29 18:39:42 CEST 2006
More information about the Python-Dev mailing list
Thu Jun 29 18:39:42 CEST 2006
- Previous message: [Python-Dev] PEP 328 and PEP 338, redux
- Next message: [Python-Dev] PEP 328 and PEP 338, redux
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/29/06, Giovanni Bajo <rasky at develer.com> wrote: > Real-world usage case for import __main__? Otherwise, I say screw it :) [...] > My personal argument is that if __name__ == '__main__' is totally > counter-intuitve and unpythonic. It also proves my memory: after many years, > I still have to think a couple of seconds before rememebering whether I > should use __file__, __name__ or __main__ and where to put the damn quotes. > The fact that you're comparing a variable name and a string literal which > seems very similar (both with the double underscore syntax) is totally > confusing at best. > > Also, try teaching it to a beginner and he will go "huh wtf". To fully > understand it, you must understand how import exactly works (that is, the > fact that importing a module equals evaluating all of its statement one by > one). A function called __main__ which is magically invoked by the python > itself is much much easier to grasp. A different, clearer spelling for the > if condition (like: "if not __imported__") would help as well. You need to watch your attitude, and try to present better arguments than "I don't like it". -- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] PEP 328 and PEP 338, redux
- Next message: [Python-Dev] PEP 328 and PEP 338, redux
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list