I have a general question and a specific question. First the general one:
(1) When is it okay to use C99 code in the Python core? More particularly,
is it considered acceptable to use widely-implemented library functions that
are specified in C99 but not ANSI C, or widely-implemented features
2008/7/5 Mark Dickinson [EMAIL PROTECTED]:
I have a general question and a specific question. First the general one:
(1) When is it okay to use C99 code in the Python core? More particularly,
is it considered acceptable to use widely-implemented library functions that
are specified in C99
(1) When is it okay to use C99 code in the Python core? More particularly,
is it considered acceptable to use widely-implemented library functions that
are specified in C99 but not ANSI C, or widely-implemented features that
are new to C99?
[C99 is also ANSI C, IIUC. ANSI has adopted ISO/IEC
On Tue, Jul 1, 2008 at 8:29 PM, Barry Warsaw [EMAIL PROTECTED] wrote:
On Jul 1, 2008, at 10:42 PM, Benjamin Peterson wrote:
On Tue, Jul 1, 2008 at 8:44 PM, Barry Warsaw [EMAIL PROTECTED] wrote:
On Jul 1, 2008, at 7:27 PM, Brett Cannon wrote:
Is a Google Calendar kept by anyone that lists
Hello,
Short story: bytearray and array.array by construction allow user code to
reallocate their internal memory buffer. But a raw pointer to the said buffer
can also be obtained by another thread, and used after releasing the GIL (for
CPU-intensive operations like compression). As a
Short story: bytearray and array.array by construction allow user code to
reallocate their internal memory buffer. But a raw pointer to the said buffer
can also be obtained by another thread, and used after releasing the GIL (for
CPU-intensive operations like compression). As a consequence,
On Thu, Jun 26, 2008 at 8:18 AM, [EMAIL PROTECTED] wrote:
Today on planetpython.org, Doug Hellman announced the June issue of Python
magazine. The cover story this month is about Pybots, the fantastic
automation system that has been put in place to make sure new releases of
Python software
A few years ago (yes, it's been that long), I proposed adding a new
format code to struct that would pack integers as strings, similar to
the 's' format code. In particular, struct.pack('60G', v) would be a
60-byte big-endian unsigned integer as a string. The feature request
is