[Python-Dev] listcomps vs. for loops
Guido van Rossum
guido at python.org
Mon Oct 20 13:48:00 EDT 2003
More information about the Python-Dev mailing list
Mon Oct 20 13:48:00 EDT 2003
- Previous message: [Python-Dev] listcomps vs. for loops
- Next message: [Python-Dev] listcomps vs. for loops
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> >> We are indeed sure (sadly) that list comprehensions leak control > >> variable names. > > > > But they shouldn't. It can be fixed by renaming them (e.g. numeric > > names with a leading dot). > > ?!?! When listcomps were introduced, you were strongly against any > changes that would make it difficult to switch back and forth between a > listcomp and its corresponding equivalent for loop. I don't recall what I said then. Did I say it was a feature that L = [x for x in R] print x would print the last item of R? > Are you changing your position or are you suggesting that for loops > should grow private names? No, only list comps. --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] listcomps vs. for loops
- Next message: [Python-Dev] listcomps vs. for loops
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list