➜

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 vstinner
Recipients vstinner
Date 2010-05-29.02:24:18
SpamBayes Score 0.0036138552
Marked as misclassified No
Message-id <1275099860.74.0.46695580149.issue8850@psf.upfronthosting.co.za>
In-reply-to
Content 
"w" format is dangerous because it doesn't give the size of the buffer: the caller may write outside the buffer (buffer overflow).

"w*" and "w#" formats are fine.

It looks like "w" format is not used in trunk nor py3k (only w# and w*).
History
Date User Action Args
2010-05-29 02:24:20vstinnersetrecipients: + vstinner
2010-05-29 02:24:20vstinnersetmessageid: <1275099860.74.0.46695580149.issue8850@psf.upfronthosting.co.za>
2010-05-29 02:24:18vstinnerlinkissue8850 messages
2010-05-29 02:24:18vstinnercreate