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, belopolsky, dgreiman, eli.bendersky, ext-, gustavo, pitrou |
| Date | 2013年05月13日.21:41:43 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1368481300.4048.13.camel@fsol> |
| In-reply-to | <1368480478.57.0.928335325039.issue1772673@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> Antoine, I was referring to the discussion linked earlier > (http://mail.python.org/pipermail/python-dev/2006-February/060689.html). Ok, I've read it through. The problem is specifically with pointers-to-pointers: http://mail.python.org/pipermail/python-dev/2006-February/060849.html And indeed, PyArg_ParseTupleAndKeywords() got its "const char **" argument changed back to "char **". But the other consts have stayed (such as the "const char *" argument to the same PyArg_ParseTupleAndKeywords()). So it looks like the patch, in essence, is legit. (of course, in practice, it probably won't apply cleanly, since it's very old; and perhaps it's incomplete too) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013年05月13日 21:41:43 | pitrou | set | recipients: + pitrou, amaury.forgeotdarc, belopolsky, gustavo, dgreiman, ext-, eli.bendersky |
| 2013年05月13日 21:41:43 | pitrou | link | issue1772673 messages |
| 2013年05月13日 21:41:43 | pitrou | create | |