"Martin v. Löwis" martin at v.loewis.de
Tue Mar 22 01:49:44 CET 2011

• Previous message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
• Next message: [Python-Dev] [GSoC] Porting on RPM3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> But now that I think about it, I guess it's a lot easier to miss a place
> like PyArg_Parse*() when manually migrating code. The conversion of the
> type string is really not obvious and the C compiler can't provide any
> help. 

I actually have a GCC extension allowing the compiler to detect type
errors in PyArg_ParseTuple.

Regards,
Martin

---

• Previous message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
• Next message: [Python-Dev] [GSoC] Porting on RPM3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list