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 djmitche
Recipients Rhamphoryncus, akuchling, arigo, djmitche, dugan, jafo, jepler, loewis
Date 2008-05-10.18:43:15
SpamBayes Score 0.009371724
Marked as misclassified No
Message-id <1210444996.36.0.287863073175.issue1174606@psf.upfronthosting.co.za>
In-reply-to
Content
While it is a sensible fix for the signed/unsigned problem, David's patch 
still fails regrtest on my system (amd64), after OOM-killing random other 
processes :(

Andrew's suggestion makes a lot of sense here.  Does it make sense for 
new_buffersize to return (PY_SSIZE_T_MAX+1) in this case, to trigger an 
overflow (in addition to David's patch)?
History
Date User Action Args
2008-05-10 18:43:16djmitchesetspambayes_score: 0.00937172 -> 0.009371724
recipients: + djmitche, loewis, akuchling, arigo, jepler, jafo, rhamphoryncus.historic, dugan
2008-05-10 18:43:16djmitchesetspambayes_score: 0.00937172 -> 0.00937172
messageid: <1210444996.36.0.287863073175.issue1174606@psf.upfronthosting.co.za>
2008-05-10 18:43:15djmitchelinkissue1174606 messages
2008-05-10 18:43:15djmitchecreate