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 | amaury.forgeotdarc, giampaolo.rodola, gpolo, pitrou |
| Date | 2008年07月05日.18:35:47 |
| SpamBayes Score | 0.012072028 |
| Marked as misclassified | No |
| Message-id | <1215282949.16.0.548133345407.issue3139@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
If I try to follow the chain the consequences:
- all PyArg_ParseTuple("s#") calls that release the GIL afterwards
should be re-written to use another API (which one I don't know exactly,
but hopefully the appropriate functions are already provided by the
buffer API); this applies to third-party extension modules as well
- consequently, forward compatibility is broken in an important way
(but it would probably be ok for py3k)
- perhaps the bytearray type should not have been backported to 2.6, or
perhaps it should carry a big warning in the documentation |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月05日 18:35:49 | pitrou | set | spambayes_score: 0.012072 -> 0.012072028 recipients: + pitrou, amaury.forgeotdarc, giampaolo.rodola, gpolo |
| 2008年07月05日 18:35:49 | pitrou | set | spambayes_score: 0.012072 -> 0.012072 messageid: <1215282949.16.0.548133345407.issue3139@psf.upfronthosting.co.za> |
| 2008年07月05日 18:35:48 | pitrou | link | issue3139 messages |
| 2008年07月05日 18:35:47 | pitrou | create | |