[Python-Dev] O(1) deletes from the front of bytearray (was: Re: Adding bytes.frombuffer() constructor to PEP 467 (was: [Python-ideas] Adding bytes.frombuffer() constructor)
Victor Stinner
victor.stinner at gmail.com
Wed Oct 12 07:55:34 EDT 2016
More information about the Python-Dev mailing list
Wed Oct 12 07:55:34 EDT 2016
- Previous message (by thread): [Python-Dev] O(1) deletes from the front of bytearray (was: Re: Adding bytes.frombuffer() constructor to PEP 467 (was: [Python-ideas] Adding bytes.frombuffer() constructor)
- Next message (by thread): [Python-Dev] O(1) deletes from the front of bytearray (was: Re: Adding bytes.frombuffer() constructor to PEP 467 (was: [Python-ideas] Adding bytes.frombuffer() constructor)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2016-10-12 10:01 GMT+02:00 Nathaniel Smith <njs at pobox.com>: > It's more complicated than that -- the right algorithm is the one that > Antoine implemented in 3.4. > (...) > My point is that > forcing everyone who writes network code in Python to do that is > silly, especially given that CPython's apparently been shipping this > feature for years. "For years" means since March 2014, Python 3.4.0 release, so 2 years ago. We can document the optimization as a CPython implementation detail and explain that it's only in Python >= 3.4. So an application which should work on Python 2.7 as well cannot rely on this optimization for example. Victor
- Previous message (by thread): [Python-Dev] O(1) deletes from the front of bytearray (was: Re: Adding bytes.frombuffer() constructor to PEP 467 (was: [Python-ideas] Adding bytes.frombuffer() constructor)
- Next message (by thread): [Python-Dev] O(1) deletes from the front of bytearray (was: Re: Adding bytes.frombuffer() constructor to PEP 467 (was: [Python-ideas] Adding bytes.frombuffer() constructor)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list