[Python-Dev] What do we do about bad slicing and possible crashes (issue 27867) (original) (raw)
Stefan Krah stefan at bytereef.org
Tue Aug 30 09:17:01 EDT 2016
- Previous message (by thread): [Python-Dev] What do we do about bad slicing and possible crashes (issue 27867)
- Next message (by thread): [Python-Dev] What do we do about bad slicing and possible crashes (issue 27867)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Aug 30, 2016 at 03:11:25PM +0200, Maciej Fijalkowski wrote:
It's more complicated - if the third party rely on the code working when one thread slices while the other thread modifies that gives implicit atomicity requirements. Those specific requirements are very hard to maintain across the python versions and python implementations. Replicating the exact CPython behavior (for each CPython version too!) is a major nightmare for such specific scenarios.
I propose the following: * we raise an error if detected
+1
Stefan Krah
- Previous message (by thread): [Python-Dev] What do we do about bad slicing and possible crashes (issue 27867)
- Next message (by thread): [Python-Dev] What do we do about bad slicing and possible crashes (issue 27867)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]