Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/109763.html below:

[Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple

• 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 ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4