> > would it be good to try and turn that into an exception? like if the
> PixelArray would check the lock count or something?
Surfaces do not feature a tracking of lock counts at the moment. And
checking for an existing lock might mess up user intendend locking
behaviour, I think.
I was only thinking it would check for a count of 0 - it is a clearly invalid lock count to have while PixelArray is still in existence, regardless of what the user did
The problem as I see it is that seg faults and corrupted memory are both really really bad bugs that I wish I could never get when using python as they are the sort of bugs whose behavior is inconsistent so you could miss them when developing but leave in production, and because they are not strongly tied to their actual cause
Also, if people aren't sticking to the docs, then the docs aren't effective