➜

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 alexandre.vassalotti
Recipients alexandre.vassalotti
Date 2007-10-11.03:00:25
SpamBayes Score 0.07359603
Marked as misclassified No
Message-id <1192071626.91.0.943640538165.issue1260@psf.upfronthosting.co.za>
In-reply-to
Content 
This patch removes the buffer API from PyUnicode, as specified by PEP
3137. All the unit tests passes. However, I believe there is a few
function calls to PyArg API that could become problematic if they are
given a PyUnicode object:

  % egrep -R --include='*.c' 'PyArg.*Parse.*"[^;:]*[cwt].*"' py3k/

I haven't checked these function calls yet. So, it would probably be a
good idea to wait I do so before committing this patch.
Files
File name Uploaded
unicode_rm_buf_api.patch alexandre.vassalotti, 2007-10-11.03:00:25
History
Date User Action Args
2007-10-11 03:00:27alexandre.vassalottisetspambayes_score: 0.073596 -> 0.07359603
recipients: + alexandre.vassalotti
2007-10-11 03:00:26alexandre.vassalottisetspambayes_score: 0.073596 -> 0.073596
messageid: <1192071626.91.0.943640538165.issue1260@psf.upfronthosting.co.za>
2007-10-11 03:00:26alexandre.vassalottilinkissue1260 messages
2007-10-11 03:00:26alexandre.vassalotticreate