Re: [Python-3000] Possible py3k problem.

2008-11-19 Thread python-3000
UB) I'm not sure, that it will segfault too. But can't test it on Opteron, sorry for that. To clear out the situation, just want to ask, what is the type of callback variable and how it differs from the type of GSL_FUNCTION(...) expression. _____

Re: [Python-3000] PEP: rename it.next() to it.__next__(), add a next() built-in

2007-03-05 Thread python
aking it potentially difficult and/or > buggy to write forward or backward compatible code, > 3) it smells like gratuitous breakage. And, more importantly, it is butt-ugly. Raymond _______ Python-3000 mailing list Python-3000@python.org http://mail.p

Re: [Python-3000] PEP: rename it.next() to it.__next__(), add a next() built-in

2007-03-05 Thread python
hing the functionality into the next() method. ___________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com

Re: [Python-3000] PEP: rename it.next() to it.__next__(), add a next() built-in

2007-03-05 Thread python
; def f(x): ...while x > 1: ...yield x ...if x % 2 == 0: ...x //= 2 ...else: ...x = x * 3 + 1 ... >>> g = f(12) >>> g() 12 >>> g() 6 >>> g() 3 >>> g() 10 Raymond Hettinger ___