[Python-ideas] Python-ideas Digest, Vol 131, Issue 106
Chris Angelico
rosuav at gmail.com
Tue Oct 31 04:01:34 EDT 2017
More information about the Python-ideas mailing list
Tue Oct 31 04:01:34 EDT 2017
- Previous message (by thread): [Python-ideas] Python-ideas Digest, Vol 131, Issue 106
- Next message (by thread): [Python-ideas] Python-ideas Digest, Vol 131, Issue 106
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Oct 31, 2017 at 6:46 PM, Steven D'Aprano <steve at pearwood.info> wrote: > On Tue, Oct 31, 2017 at 06:02:34PM +1100, Chris Angelico wrote: >> One small change: If you use next(i) instead of i.next(), your code >> should work on both Py2 and Py3. But other than that, I think it's >> exactly the same as most people would expect of this function. > > Not me. As far as I can tell, that's semantically equivalent to: > > def single(i): > result, = i > return result > > apart from slightly different error messages. I saw the original code as being like the itertools explanatory functions - you wouldn't actually USE those functions, but they tell you what's going on when you use the simpler, faster, more compact form. ChrisA
- Previous message (by thread): [Python-ideas] Python-ideas Digest, Vol 131, Issue 106
- Next message (by thread): [Python-ideas] Python-ideas Digest, Vol 131, Issue 106
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list