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 ncoghlan
Recipients jcon, kermode, mark.dickinson, ncoghlan, petri.lehtinen, pitrou, pv, rupole, skrah, teoliphant, vstinner
Date 2011-07-04.12:30:50
SpamBayes Score 6.9919835e-05
Marked as misclassified No
Message-id <1309782651.36.0.102425521749.issue10181@psf.upfronthosting.co.za>
In-reply-to
Content
As far as the rule of disallowing shape changes while a buffer is exported, I actually think that's a more sane approach as well. However, I've been burned enough times by going "nobody would be insane enough to rely on that, would they?" that I'm seriously reluctant to impose additional backwards incompatible rules on a published spec when it isn't *too* difficult to adjust the infrastructure to better handle the existing complexity.
History
Date User Action Args
2011-07-04 12:30:51ncoghlansetrecipients: + ncoghlan, teoliphant, mark.dickinson, rupole, kermode, pitrou, vstinner, pv, skrah, jcon, petri.lehtinen
2011-07-04 12:30:51ncoghlansetmessageid: <1309782651.36.0.102425521749.issue10181@psf.upfronthosting.co.za>
2011-07-04 12:30:50ncoghlanlinkissue10181 messages
2011-07-04 12:30:50ncoghlancreate