Message 65068 - Python tracker

➜

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	gregory.p.smith
Recipients	amaury.forgeotdarc, gregory.p.smith, nnorwitz, teoliphant
Date	2008-04-07.07:42:05
SpamBayes Score	0.037816692
Marked as misclassified	No
Message-id	<1207554126.92.0.939703562138.issue2538@psf.upfronthosting.co.za>
In-reply-to

Content
This patch looks good. One question: in Objects/abstract.c in PyBuffer_FillInfo, why is it even testing for the PyBUF_LOCK flag at all? PEP 3118 says its valid for both reading and writing (if the underlying object supports locked access). BTW, I is someone is going to merge any py3k buffer api related changes back into the backport that is in 2.6?

This patch looks good.

One question: in Objects/abstract.c in PyBuffer_FillInfo, why is it even
testing for the PyBUF_LOCK flag at all?  PEP 3118 says its valid for
both reading and writing (if the underlying object supports locked access).

BTW, I is someone is going to merge any py3k buffer api related changes
back into the backport that is in 2.6?

History
Date	User	Action	Args
2008-04-07 07:42:07	gregory.p.smith	set	spambayes_score: 0.0378167 -> 0.037816692 recipients: + gregory.p.smith, nnorwitz, teoliphant, amaury.forgeotdarc
2008-04-07 07:42:06	gregory.p.smith	set	spambayes_score: 0.0378167 -> 0.0378167 messageid: <1207554126.92.0.939703562138.issue2538@psf.upfronthosting.co.za>
2008-04-07 07:42:05	gregory.p.smith	link	issue2538 messages
2008-04-07 07:42:05	gregory.p.smith	create