summaryrefslogtreecommitdiffstats
path: root/Include
Commit message (Collapse)AuthorAgeFilesLines
* Issue #17937: Try harder to collect cyclic garbage at shutdown.Antoine Pitrou2013-05-181-0/+4
|
* rather than passing locals to the class body, just execute the class body in ↵Benjamin Peterson2013-05-161-1/+0
| | | | the proper environment
* hide the __class__ closure from the class body (#12370)Benjamin Peterson2013-05-151-0/+3
|
* Backout c89febab4648 following private feedback by Guido.Antoine Pitrou2013-05-142-10/+0
| | | | (Issue #17807: Generators can now be finalized even when they are part of a reference cycle)
* remove support GCC PyArg_ParseTuple format patch, last seen in 2006Benjamin Peterson2013-05-132-10/+1
|
* Issue #17912: Use a doubly linked-list for thread states.Charles-Francois Natali2013-05-081-0/+1
|
* Issue #17807: Generators can now be finalized even when they are part of a ↵Antoine Pitrou2013-05-082-0/+10
| | | | reference cycle.
* Issue #1545463: At shutdown, defer finalization of codec modules so that ↵Antoine Pitrou2013-05-081-0/+6
| | | | | | stderr remains usable. (should fix Windows buildbot failures on test_gc)
* Issue #1545463: Global variables caught in reference cycles are now ↵Antoine Pitrou2013-05-061-0/+1
| | | | garbage-collected at shutdown.
* Issue #17094: Clear stale thread states after fork().Antoine Pitrou2013-05-051-0/+1
| | | | | | | Note that this is a potentially disruptive change since it may release some system resources which would otherwise remain perpetually alive (e.g. database connections kept in thread-local storage).
* Issue #17408: Avoid using an obsolete instance of the copyreg module when ↵Antoine Pitrou2013-05-041-0/+1
|\ | | | | | | the interpreter is shutdown and then started again.
| * Issue #17408: Avoid using an obsolete instance of the copyreg module when ↵Antoine Pitrou2013-05-041-0/+1
| | | | | | | | the interpreter is shutdown and then started again.
| * Post-release update for 3.3.1Georg Brandl2013-04-061-1/+1
| |
| * Bump to 3.3.1.v3.3.1Georg Brandl2013-04-061-3/+3
| |
| * Bump to 3.3.1rc1.Georg Brandl2013-03-231-4/+4
| |
* | Closes #17892: Fix the name of _PyObject_CallMethodObjIdArgsAlexandre Vassalotti2013-05-021-2/+1
| |
* | check local class namespace before reaching for cells (closes #17853)Benjamin Peterson2013-04-301-0/+1
| |
* | fix typo in a commentVictor Stinner2013-04-181-1/+1
| |
* | Close #17694: Add minimum length to _PyUnicodeWriterVictor Stinner2013-04-171-7/+13
| | | | | | | | | | | | | | | | | | | | | | | | * Add also min_char attribute to _PyUnicodeWriter structure (currently unused) * _PyUnicodeWriter_Init() has no more argument (except the writer itself): min_length and overallocate must be set explicitly * In error handlers, only enable overallocation if the replacement string is longer than 1 character * CJK decoders don't use overallocation anymore * Set min_length, instead of preallocating memory using _PyUnicodeWriter_Prepare(), in many decoders * _PyUnicode_DecodeUnicodeInternal() checks for integer overflow
* | Close #17693: Rewrite CJK decoders to use the _PyUnicodeWriter API instead ofVictor Stinner2013-04-111-0/+7
| | | | | | | | | | | | the legacy Py_UNICODE API. Add also a new _PyUnicodeWriter_WriteChar() function.
* | Add _PyUnicodeWriter_WriteSubstring() functionVictor Stinner2013-04-021-0/+9
| | | | | | | | | | | | | | | | | | Write a function to enable more optimizations: * If the substring is the whole string and overallocation is disabled, just keep a reference to the string, don't copy characters * Avoid a call to the expensive _PyUnicode_FindMaxChar() function when possible
* | Issue #17522: Add the PyGILState_Check() API.Kristján Valur Jónsson2013-03-231-0/+5
| |
* | Issue #16475: Support object instancing, recursion and interned stringsKristján Valur Jónsson2013-03-201-1/+1
| | | | | | | | in marshal
* | unify some ast.argument's attrs; change Attribute column offset (closes #16795)Benjamin Peterson2013-03-181-10/+9
| | | | | | | | Patch from Sven Brauch.
* | make some freezing related stuff constBenjamin Peterson2013-03-131-3/+3
| |
* | Issue #17047: remove doubled words added in 3.4,Terry Jan Reedy2013-03-111-1/+1
| | | | | | | | as reported by Serhiy Storchaka and Matthew Barnett.
* | Add PyDict_SetDefault. (closes #17327)Benjamin Peterson2013-03-081-0/+2
| | | | | | | | Patch by Stefan Behnel and I.
* | Issue #1783: Remove declarations of nonexistent private variables.Serhiy Storchaka2013-02-011-4/+0
|\ \ | |/
| * Issue #1783: Remove declarations of nonexistent private variables.Serhiy Storchaka2013-02-011-4/+0
| |\
| | * Issue #1783: Remove declarations of nonexistent private variables.Serhiy Storchaka2013-02-011-4/+0
| | |
| * | Issue #15989: Fix several occurrences of integer overflowSerhiy Storchaka2013-01-191-0/+3
| |\ \ | | |/ | | | | | | | | | | | | when result of PyLong_AsLong() narrowed to int without checks. This is a backport of changesets 13e2e44db99d and 525407d89277.
| | * Issue #15989: Fix several occurrences of integer overflowSerhiy Storchaka2013-01-191-0/+3
| | | | | | | | | | | | | | | | | | when result of PyLong_AsLong() narrowed to int without checks. This is a backport of changesets 13e2e44db99d and 525407d89277.
* | | Issue #15989: Fix several occurrences of integer overflowSerhiy Storchaka2013-01-141-0/+3
| | | | | | | | | | | | when result of PyLong_AsLong() narrowed to int without checks.
* | | Issue #16881: Fix Py_ARRAY_LENGTH macro for GCC < 3.1.Christian Heimes2013-01-061-2/+5
|\ \ \ | |/ /
| * | Issue #16881: Fix Py_ARRAY_LENGTH macro for GCC < 3.1.Christian Heimes2013-01-061-2/+5
| | |
* | | Revert back PyCFunction_New macro. Keep PyCFunction_NewEx usage in python ↵Andrew Svetlov2012-12-261-1/+1
| | | | | | | | | | | | core modules (#15422)
* | | Issue #15422: get rid of PyCFunction_New macroAndrew Svetlov2012-12-251-1/+1
| | |
* | | Fix the internals of our hash functions to used unsigned values during hashGregory P. Smith2012-12-111-1/+1
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | computation as the overflow behavior of signed integers is undefined. NOTE: This change is smaller compared to 3.2 as much of this cleanup had already been done. I added the comment that my change in 3.2 added so that the code would match up. Otherwise this just adds or synchronizes appropriate UL designations on some constants to be pedantic. In practice we require compiling everything with -fwrapv which forces overflow to be defined as twos compliment but this keeps the code cleaner for checkers or in the case where someone has compiled it without -fwrapv or their compiler's equivalent. We could work to get rid of the -fwrapv requirement in 3.4 but that requires more planning. Found by Clang trunk's Undefined Behavior Sanitizer (UBSan). Cleanup only - no functionality or hash values change.
| * | Fix the internals of our hash functions to used unsigned values during hashGregory P. Smith2012-12-111-1/+1
| |\ \ | | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | computation as the overflow behavior of signed integers is undefined. NOTE: This change is smaller compared to 3.2 as much of this cleanup had already been done. I added the comment that my change in 3.2 added so that the code would match up. Otherwise this just adds or synchronizes appropriate UL designations on some constants to be pedantic. In practice we require compiling everything with -fwrapv which forces overflow to be defined as twos compliment but this keeps the code cleaner for checkers or in the case where someone has compiled it without -fwrapv or their compiler's equivalent. Found by Clang trunk's Undefined Behavior Sanitizer (UBSan). Cleanup only - no functionality or hash values change.
| | * Fix the internals of our hash functions to used unsigned values during hashGregory P. Smith2012-12-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | computation as the overflow behavior of signed integers is undefined. In practice we require compiling everything with -fwrapv which forces overflow to be defined as twos compliment but this keeps the code cleaner for checkers or in the case where someone has compiled it without -fwrapv or their compiler's equivalent. Found by Clang trunk's Undefined Behavior Sanitizer (UBSan). Cleanup only - no functionality or hash values change.
* | | Using 'long double' to force this structure to be worst case aligned is noGregory P. Smith2012-12-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | longer required as of Python 2.5+ when the gc_refs changed from an int (4 bytes) to a Py_ssize_t (8 bytes) as the minimum size is 16 bytes. The use of a 'long double' triggered a warning by Clang trunk's Undefined-Behavior Sanitizer as on many platforms a long double requires 16-byte alignment but the Python memory allocator only guarantees 8 byte alignment. So our code would allocate and use these structures with technically improper alignment. Though it didn't matter since the 'dummy' field is never used. This silences that warning. Spelunking into code history, the double was added in 2001 to force better alignment on some platforms and changed to a long double in 2002 to appease Tru64. That issue should no loner be present since the upgrade from int to Py_ssize_t where the minimum structure size increased to 16 (unless anyone knows of a platform where ssize_t is 4 bytes?) or 24 bytes depending on if the build uses 4 or 8 byte pointers. We can probably get rid of the double and this union hack all together today. That is a slightly more invasive change that can be left for later. A more correct non-hacky alternative if any alignment issues are still found would be to use a compiler specific alignment declaration on the structure and determine which value to use at configure time.
* | | Issue #13390: New function :func:`sys.getallocatedblocks()` returns the ↵Antoine Pitrou2012-12-091-0/+2
| | | | | | | | | | | | | | | | | | number of memory blocks currently allocated. Also, the ``-R`` option to regrtest uses this function to guard against memory allocation leaks.
* | | Issue #16602: When a weakref's target was part of a long deallocation chain, ↵Antoine Pitrou2012-12-081-1/+11
|\ \ \ | |/ / | | | | | | | | | | | | the object could remain reachable through its weakref even though its refcount had dropped to zero. Thanks to Eugene Toder for diagnosing and reporting the issue.
| * | Issue #16602: When a weakref's target was part of a long deallocation chain, ↵Antoine Pitrou2012-12-081-1/+11
| |\ \ | | |/ | | | | | | | | | | | | the object could remain reachable through its weakref even though its refcount had dropped to zero. Thanks to Eugene Toder for diagnosing and reporting the issue.
| | * Issue #16602: When a weakref's target was part of a long deallocation chain, ↵Antoine Pitrou2012-12-081-1/+11
| | | | | | | | | | | | | | | | | | the object could remain reachable through its weakref even though its refcount had dropped to zero. Thanks to Eugene Toder for diagnosing and reporting the issue.
* | | create NameConstant AST class for None, True, and False literals (closes #16619)Benjamin Peterson2012-12-062-2/+11
| | |
* | | Update comment: SAVE_EXC_STATE and SWAP_EXC_STATE macroses are ↵Andrew Svetlov2012-12-051-2/+2
|\ \ \ | |/ / | | | | | | saave_exc_state and swap_exc_state functions now.
| * | Update comment: SAVE_EXC_STATE and SWAP_EXC_STATE macroses are ↵Andrew Svetlov2012-12-051-2/+2
| | | | | | | | | | | | saave_exc_state and swap_exc_state functions now.
| * | Issue 10052: merge fix from 3.2.Mark Dickinson2012-12-021-8/+21
| |\ \ | | |/
| | * Issue 10052: fix failed uint32_t / uint64_t / int32_t / int64_t detection on ↵Mark Dickinson2012-12-021-8/+21
| | | | | | | | | | | | some platforms.
generated by cgit v0.12 at 2024-11-24 12:46:37 (GMT)