homepage

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 loewis, pitrou, vstinner
Date 2010年06月13日.21:36:19
SpamBayes Score 0.0012244997
Marked as misclassified No
Message-id <1276464982.06.0.0448986383391.issue8850@psf.upfronthosting.co.za>
In-reply-to
Content
"w#" is not only useless but also not used in py3k source code. "w" is also not used. Only "w*" is used by fnctl and socket modules.
The problem with w# is that the caller cannot "release" the buffer and so we cannot lock the buffer. I don't know exactly what happens if you get a pointer to a bytearray, release the GIL and then use it, whereas another thread modifies and/or destroys the bytearray object. (I suppose that something bad will happen, like a segfault)
History
Date User Action Args
2010年06月13日 21:36:22vstinnersetrecipients: + vstinner, loewis, pitrou
2010年06月13日 21:36:22vstinnersetmessageid: <1276464982.06.0.0448986383391.issue8850@psf.upfronthosting.co.za>
2010年06月13日 21:36:19vstinnerlinkissue8850 messages
2010年06月13日 21:36:19vstinnercreate

AltStyle によって変換されたページ (->オリジナル) /