[Python-Dev] threading.Semaphore()'s counter can become negative for non-ints (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Mon Jan 30 23:19:42 CET 2012
- Previous message: [Python-Dev] threading.Semaphore()'s counter can become negative for non-ints
- Next message: [Python-Dev] threading.Semaphore()'s counter can become negative for non-ints
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Jan 31, 2012 at 8:11 AM, Matt Joiner <anacrolix at gmail.com> wrote:
It's also potentially lossy if you incremented and decremented until integer precision is lost. My vote is for an int type check. No casting.
operator.index() is built for that purpose (it's what we use these days to restrict slicing to integers).
+1 for the type restriction from me.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] threading.Semaphore()'s counter can become negative for non-ints
- Next message: [Python-Dev] threading.Semaphore()'s counter can become negative for non-ints
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]