[Python-Dev] State of PEP-3118 (memoryview part) (original) (raw)
Stefan Krah stefan at bytereef.org
Wed Feb 29 20:34:49 CET 2012
- Previous message: [Python-Dev] State of PEP-3118 (memoryview part)
- Next message: [Python-Dev] State of PEP-3118 (memoryview part)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Options 2) and 3) would ideally entail one backwards incompatible bugfix: In 2.7 and 3.2 assignment to a memoryview with format 'B' rejects integers but accepts byte objects, but according to the struct syntax mandated by the PEP it should be the other way round. Maybe a compromise could be made to accept both in the backport? That would avoid breaking old code while allowing code that does the right thing to work.
This could definitely be done. But backporting is beginning to look unlikely, since we currently have three +1 for "too complex to backport".
I'm not strongly in favor of backporting myself. The main reason for me would be to prevent having additional 2->3 or 3->2 porting obstacles.
Stefan Krah
- Previous message: [Python-Dev] State of PEP-3118 (memoryview part)
- Next message: [Python-Dev] State of PEP-3118 (memoryview part)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]