[Python-Dev] About raising NotPortableWarning for CPython specific code
Neil Schemenauer
nas at arctrix.com
Sun Mar 13 02:23:05 CET 2011
More information about the Python-Dev mailing list
Sun Mar 13 02:23:05 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 ]
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. Neil
- 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