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

Showing content from https://mail.python.org/pipermail/python-dev/2012-November/122547.html below:

[Python-Dev] ctypes is not an acceptable implementation strategy for modules in the standard library?

• Previous message: [Python-Dev] ctypes is not an acceptable implementation strategy for modules in the standard library?
• Next message: [Python-Dev] ctypes is not an acceptable implementation strategy for modules in the standard library?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 2012-11-05, at 10:32 , Ronald Oussoren wrote:
>> My arguments for ctypes:
>> 1. doesn't require compilation
>> 2. easier to maintain (no C/toolchain knowledge/ownership needed)
>> 3. pure Python is impossible to exploit (unlike pure C)
> 
> That's not not quite true, python code that uses ctypes can still cause buffer overflows and the like

Such as segfaulting the interpreter. I seem to reliably segfault
everything every time I try to use ctypes.

• Previous message: [Python-Dev] ctypes is not an acceptable implementation strategy for modules in the standard library?
• Next message: [Python-Dev] ctypes is not an acceptable implementation strategy for modules in the standard library?
• 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