[Python-Dev] About raising NotPortableWarning for CPython specific code
Terry Reedy
tjreedy at udel.edu
Sun Mar 13 03:19:44 CET 2011
More information about the Python-Dev mailing list
Sun Mar 13 03:19:44 CET 2011
- Previous message: [Python-Dev] About raising NotPortableWarning for CPython specific code
- Next message: [Python-Dev] About raising NotPortableWarning for CPython specific code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 3/12/2011 8:23 PM, Neil Schemenauer wrote: > Greg Ewing<greg.ewing at canterbury.ac.nz> wrote: >> So am I. It seems to result from the hisorical mess >> of distinguishing between numeric and sequence operations >> at the C level but not the Python level. I think CPython >> should be moving in the direction of eliminating that >> distinction, not expecting all other Python implementations >> to copy it. > > As a person responsible for part of the mess, I agree. I would hope > this could be cleaned up in Python 3 without causing too much > trouble for developers. I opened the issue http://bugs.python.org/issue11477 but I won't be writing the patch ;-). -- Terry Jan Reedy
- Previous message: [Python-Dev] About raising NotPortableWarning for CPython specific code
- Next message: [Python-Dev] About raising NotPortableWarning for CPython specific code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list