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 pitrou
Recipients chuck, exarkun, georg.brandl, gregory.p.smith, ivank, loewis, pitrou
Date 2009-09-29.10:56:42
SpamBayes Score 1.6945089e-05
Marked as misclassified No
Message-id <1254221807.36.0.262703180377.issue6071@psf.upfronthosting.co.za>
In-reply-to
Content
After thinking about it, we should remover the bf_releasebuffer checks
when using the old typecodes '#' (the doc should also clearly state that
these are unsafe and '*' is preferred).

If a type chooses to implement the /old/ buffer API and if a method
requires the /old/ buffer API instead of the new one (that is, by using
a '#' typecode), we have to accept these choices.

Here's a patch for trunk, combining the new buffer API for `array` and
the checks removal in getargs.c.
History
Date User Action Args
2009-09-29 10:56:49pitrousetrecipients: + pitrou, loewis, georg.brandl, gregory.p.smith, exarkun, ivank, chuck
2009-09-29 10:56:47pitrousetmessageid: <1254221807.36.0.262703180377.issue6071@psf.upfronthosting.co.za>
2009-09-29 10:56:45pitroulinkissue6071 messages
2009-09-29 10:56:45pitroucreate