[Python-Dev] About raising NotPortableWarning for CPython specific code
Nick Coghlan
ncoghlan at gmail.com
Sat Mar 12 20:05:23 CET 2011
More information about the Python-Dev mailing list
Sat Mar 12 20:05:23 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 Sat, Mar 12, 2011 at 1:41 PM, Guido van Rossum <guido at python.org> wrote: > Yeah, indeed, on everything you said. The code dispatching based on > internal slots is horribly ad-hoc and likely wrong in subtle ways. Has > any of this improved in Python 3? Not that I know of - I was definitely able to replicate the weirdness in 3.2. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- 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