| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* PyCObject_AsVoidPtr() can now open capsules. This addresses
most of the remaining backwards-compatibility concerns about
the conversion of Python 2.7 from CObjects to capsules.
* CObjects were marked Pending Deprecation.
* Documentation about this pending deprecation was added to
cobject.h.
* The capsule source files were added to the legacy PC build
processes.
|
|
|
|
|
| |
function declaration, which was kept for backwards compatibility reasons,
is now removed (the macro was introduced in 1997!).
|
|
|
|
| |
references.
|
| |
|
|
|
|
| |
CObject to PyCapsule.
|
|
|
|
|
|
| |
optimization in the incoming Python 3 JIT.
Patch by Reid Kleckner!
|
| |
|
| |
|
|
|
|
| |
fatal error in low memory condition.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
and read operations on write-only file objects. On Windows, the system C
library would return a bogus result; on Solaris, it was possible to crash
the interpreter. Patch by Stefan Krah.
|
|
|
|
|
| |
long long variant of PyLong_AsLongAndOverflow. Patch by Case Van
Horsen.
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Issue #7714: Use ``gcc -dumpversion`` to detect the version of GCC on
MacOSX.
- Make configure look for util.h as well as libutil.h. The former
is the header file that on OSX contains the defition of openpty.
(Needed to compile for OSX 10.4 on OSX 10.6)
- Use the correct definition of CC to compile the pythonw executable
|
| |
|
|
|
|
|
|
| |
could crash in many places because of the PyByteArray_AS_STRING() macro
returning NULL. The macro now returns a statically allocated empty
string instead.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
(the latter renamed to _PyLong_Frexp) now use the same core code. The
exponent produced by _PyLong_Frexp now has type Py_ssize_t instead of the
previously used int, and no longer needs scaling by PyLong_SHIFT. This
frees the math module from having to know anything about the PyLong
implementation. This closes issue #5576.
|
|
|
|
| |
exceptions a docstring.
|
|
|
|
| |
pymath.c to Modules/_math.c.
|
|
|
|
| |
Thanks Case Van Horsen for the patch.
|
| |
|
|
|
|
|
|
|
|
| |
equivalent[*] check that doesn't produce compiler warnings about a 'x < 0'
check on an unsigned type.
[*] it's equivalent for inputs of type size_t or Py_ssize_t, or any smaller
unsigned or signed integer type.
|
|
|
|
|
|
|
| |
build on
an i386 based machine, but should only be active when compiling the x86 part of
the universal binary.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
multi-architecture build (in particular when the architectures don't share
a common pointer size).
Fixed the same issue for SIZEOF_PTHREAD_T.
(No update to the NEWS file because this is a bugfix for an as yet unreleased
feature)
|
|
|
|
|
|
| |
Objects/floatobject.c and Objects/complexobject.c. This should silence
compiler warnings about implicit declaration of the 'finite' function
on Solaris.
|
| |
|
|
|
|
|
|
|
|
| |
correctly-rounded
string <-> float conversions; this makes sure that the result of the round
operation is correctly rounded, and hence displays nicely using the new float
repr.
|
|
|
|
| |
PyFormat_FromStringV and PyErr_Format.
|
| |
|
| |
|
|
|
|
|
| |
pieces are being assembled. To re-enable, define the preprocessor
symbol PY_SHORT_FLOAT_REPR
|
|
|
|
|
|
|
|
|
| |
- add double endianness detection to configure script
- add configure-time check to see whether we can use inline
assembly to get and set x87 control word in configure script
- add functions to get and set x87 control word in Python/pymath.c
- add pyport.h logic to determine whether it's safe to use the
short float repr or not
|
|
|
|
|
|
|
| |
Add the Python/dtoa.c file containing the main algorithms;
add corresponding include file and include in Python.h;
include license information for Python/dtoa.c;
add dtoa.c and dtoa.h to Makefile.
|
|
|
|
| |
The debug memory api now keeps track of which external API (PyMem_* or PyObject_*) was used to allocate each block and treats any API violation as an error. Added separate _PyMem_DebugMalloc functions for the Py_Mem API instead of having it use the _PyObject_DebugMalloc functions.
|
|
|
|
|
| |
(up to 3.1 times faster in tests), by special-casing base 10 in
_PyLong_Format. (Backport of r74851 from py3k.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
acquiring the import lock around fork() calls. This prevents other threads
from having that lock while the fork happens, and is the recommended way of
dealing with such issues. There are two other locks we care about, the GIL
and the Thread Local Storage lock. The GIL is obviously held when calling
Python functions like os.fork(), and the TLS lock is explicitly reallocated
instead, while also deleting now-orphaned TLS data.
This only fixes calls to os.fork(), not extension modules or embedding
programs calling C's fork() directly. Solving that requires a new set of API
functions, and possibly a rewrite of the Python/thread_*.c mess. Add a
warning explaining the problem to the documentation in the mean time.
This also changes behaviour a little on AIX. Before, AIX (but only AIX) was
getting the import lock reallocated, seemingly to avoid this very same
problem. This is not the right approach, because the import lock is a
re-entrant one, and reallocating would do the wrong thing when forking while
holding the import lock.
Will backport to 2.6, minus the tiny AIX behaviour change.
|
| |
|
|
|
|
| |
failure on HP-UX 11.00.
|