➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients christian.heimes, serhiy.storchaka, terry.reedy
Date 2014-01-26.08:30:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content 
Coverity appears concerned about the division by q. It apparently knows inrate != 0. I do not see any division by len. If q is cleared up, I presume it will check bytes_per_frame.
History
Date User Action Args
2014-01-26 08:30:07terry.reedysetrecipients: + terry.reedy, christian.heimes, serhiy.storchaka
2014-01-26 08:30:07terry.reedysetmessageid: <[email protected]>
2014-01-26 08:30:07terry.reedylinkissue20394 messages
2014-01-26 08:30:07terry.reedycreate