Python 3000 Status Update (Long!)
I've written up a comprehensive status report on Python 3000. Please read: http://www.artima.com/weblogs/viewpost.jsp?thread=208549 -- --Guido van Rossum (home page: http://www.python.org/~guido/)
Guido van Rossum schrieb:
I've written up a comprehensive status report on Python 3000. Please read:
Thank you! Now I have something to show to interested people except "read the PEPs". A minuscule nit: the rot13 codec has no library equivalent, so it won't be supported anymore :) Georg
Georg Brandl wrote:
Guido van Rossum schrieb:
I've written up a comprehensive status report on Python 3000. Please read:
Thank you! Now I have something to show to interested people except "read the PEPs".
A minuscule nit: the rot13 codec has no library equivalent, so it won't be supported anymore :)
Given that there are valid use cases for bytes-to-bytes translations, and a common API for them would be nice, does it make sense to have an additional category of codec that is invoked via specific recoding methods on bytes objects? For example: encoded = data.encode_bytes('bz2') decoded = encoded.decode_bytes('bz2') assert data == decoded Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia --------------------------------------------------------------- http://www.boredomandlaziness.org
Guido van Rossum wrote:
I've written up a comprehensive status report on Python 3000. Please read:
One doubt: In Miscellaneus you say: Ordering comparisons (<, <=, >, >=) will raise TypeError by default instead of returning arbitrary results. Equality comparisons (==, !=) will compare for object identity (is, is not) by default. I *guess* that you're talking about comparisons between different datatypes... but you didn't explicit that in your blog. Am I right? -- . Facundo . Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/
On 6/20/07, Facundo Batista <facundo@taniquetil.com.ar> wrote:
Guido van Rossum wrote:
I've written up a comprehensive status report on Python 3000. Please read:
One doubt: In Miscellaneus you say:
Ordering comparisons (<, <=, >, >=) will raise TypeError by default instead of returning arbitrary results. Equality comparisons (==, !=) will compare for object identity (is, is not) by default.
I *guess* that you're talking about comparisons between different datatypes... but you didn't explicit that in your blog.
Am I right?
No. The *default* comparison always raises an exception. Of course, most types have a comparison that does the right thing for objects of the same type -- but they still raise an exception when compared (for ordering) to objects of different types (except subtypes or related types). -- --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (4)
-
Facundo Batista -
Georg Brandl -
Guido van Rossum -
Nick Coghlan