summaryrefslogtreecommitdiff
path: root/Python
Commit message (Collapse)AuthorAgeFilesLines
* Issue #7632: Fix a bug in dtoa.c that could lead to incorrectly-rounded ↵Mark Dickinson2010-01-121-2/+22
| | | | results.
* Issue #7632: Fix a problem with _Py_dg_strtod that could lead toMark Dickinson2010-01-121-11/+15
| | | | | crashes in debug builds, for certain long numeric strings corresponding to subnormal values.
* Update version information for AST changes in r77422.Alexandre Vassalotti2010-01-111-2/+2
|
* Issue #2333: Backport set and dict comprehensions syntax.Alexandre Vassalotti2010-01-117-159/+652
|
* Change a variable type to avoid signed overflow; replace repeated '19999' ↵Mark Dickinson2010-01-111-4/+10
| | | | constant by a define.
* Remove unused BCinfo fields and an unused macro.Mark Dickinson2010-01-101-21/+8
|
* DeprecationWarning is now silent by default.Brett Cannon2010-01-101-20/+23
| | | | | | | | | | | | This was originally suggested by Guido, discussed on the stdlib-sig mailing list, and given the OK by Guido directly to me. What this change essentially means is that Python has taken a policy of silencing warnings that are only of interest to developers by default. This should prevent users from seeing warnings which are triggered by an application being run against a new interpreter before the app developer has a chance to update their code. Closes issue #7319. Thanks to Antoine Pitrou, Ezio Melotti, and Brian Curtin for helping with the issue.
* Update the version # of Python-ast.c based on the backport of set literals fromBrett Cannon2010-01-101-2/+2
| | | | r77400.
* Issue #2335: Backport set literals syntax from Python 3.x.Alexandre Vassalotti2010-01-097-184/+345
|
* Fix typo in comment.Mark Dickinson2010-01-041-1/+1
|
* Issue #5080: turn the DeprecationWarning from float arguments passedMark Dickinson2010-01-011-2/+19
| | | | | | to integer PyArg_Parse* format codes into a TypeError. Add a DeprecationWarning for floats passed with the 'L' format code, which didn't previously have a warning.
* update copyright yearBenjamin Peterson2010-01-011-1/+1
|
* check if the attribute is set before deleting it with T_OBJECT_EX (fixes #7604)Benjamin Peterson2009-12-301-5/+15
| | | | | Also, add a note to the docs about the better behavior of T_OBJECT_EX as compared to T_OBJECT.
* #7033: add new API function PyErr_NewExceptionWithDoc, for easily giving new ↵Georg Brandl2009-12-281-0/+34
| | | | exceptions a docstring.
* Issue #7518: Move substitute definitions of C99 math functions fromMark Dickinson2009-12-211-199/+0
| | | | pymath.c to Modules/_math.c.
* account for PyObject_IsInstance's new ability to failBenjamin Peterson2009-12-132-87/+445
|
* Issue #6985: number of range() items should be constrained to lieMark Dickinson2009-12-031-4/+4
| | | | in a Py_ssize_t, not an int.
* Issue #7406: Fix some occurrences of potential signed overflow in intMark Dickinson2009-12-021-2/+6
| | | | arithmetic.
* Issue #1678380: When distinguishing between -0.0 and 0.0 inMark Dickinson2009-11-281-26/+15
| | | | | | compiler_add_o, use copysign instead of examining the first and last bytes of the double. The latter method fails for little-endian ARM, OABI, where doubles are little-endian but with the words swapped.
* round(0, "ermintrude") succeeded instead of producing a TypeError. Fix this.Mark Dickinson2009-11-241-4/+4
|
* turn goto into do while loopBenjamin Peterson2009-11-201-36/+31
|
* genexps have linenosBenjamin Peterson2009-11-201-1/+1
|
* provide line number for lambdasBenjamin Peterson2009-11-201-2/+1
|
* improve several corner cases related with argument names in parenthesisBenjamin Peterson2009-11-191-1/+16
| | | | | | | | | - Fix #7362: give a good error message for parenthesized arguments with defaults. - Add a py3k warning for any parenthesized arguments since those are not allowed in Py3. This warning is not given in tuple unpacking, since that incurs the tuple unpacking warning.
* Issue #7117, continued: Change round implementation to use the ↵Mark Dickinson2009-11-181-19/+38
| | | | | | | | 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.
* a better callable replacementBenjamin Peterson2009-11-171-1/+1
|
* Set retval on PyOS_string_to_double failure.Mark Dickinson2009-10-311-3/+9
|
* Issue #6603: Fix --with-tsc build failures on x86-64 that resultedMark Dickinson2009-10-311-1/+19
| | | | | | from a gcc inline assembler peculiarity. (gcc's "A" constraint apparently means 'rax or rdx' in 64-bit mode, not edx:eax or rdx:rax as one might expect.)
* Deprecate PyOS_ascii_strtod and PyOS_ascii_atof, and document the ↵Mark Dickinson2009-10-311-2/+12
| | | | replacement function PyOS_string_to_double.
* do a backport of r75928Benjamin Peterson2009-10-291-9/+12
| | | | | The added test does not fail without the patch, but we still fix the issue of surrogates being used in wide builds where they should not be.
* Removed PyOS_ascii_atof from marshal.c, as mentioned in issue 7117. Also ↵Eric Smith2009-10-271-11/+9
| | | | brings it more in line with py3k.
* Removed PyOS_ascii_atof from ast.c, as mentioned in issue 7117.Eric Smith2009-10-271-6/+6
|
* Finished removing _PyOS_double_to_string, as mentioned in issue 7117.Eric Smith2009-10-261-135/+0
|
* Issue #7117 (backport py3k float repr) continued:Mark Dickinson2009-10-261-93/+699
| | | | Backport pystrtod.c from py3k.
* Warn against replacing PyNumber_Add with PyNumber_InPlaceAdd in sumMark Dickinson2009-10-261-0/+9
|
* Issue #7117 (backport py3k float repr) continued:Mark Dickinson2009-10-241-0/+10
| | | | | Add sys.float_repr_style attribute ('short' if short float repr is in used; 'legacy' otherwise).
* Remove temporary define from r75653Mark Dickinson2009-10-241-2/+0
|
* Issue #7117 (backport py3k float repr) continued:Mark Dickinson2009-10-241-0/+18
| | | | | | | | | - 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
* Temporary define to avoid build failureMark Dickinson2009-10-241-0/+2
|
* Issue #7117: Prepare for backport of py3k float repr.Mark Dickinson2009-10-241-0/+2609
| | | | | | | 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.
* #7035: improve docs of the various <method>_errors() functions, and give ↵Georg Brandl2009-10-221-5/+17
| | | | them docstrings.
* Issue #1722344: threading._shutdown() is now called in Py_Finalize(), whichAntoine Pitrou2009-10-201-0/+30
| | | | | fixes the problem of some exceptions being thrown at shutdown when the interpreter is killed. Patch by Adam Olsen.
* Removed calls to PyFloat_AsReprString.Eric Smith2009-10-191-42/+63
| | | | | | | | | This is in anticipation of possibly implementing issue 7117 (short float repr). This removes the last calls to PyFloat_AsString, PyFloat_AsReprString, and PyFloat_AsStringEx, which are unsafe. Also, switch to defines for error values to bring this code more in line with the py3k branch.
* Allow core Python build to succeed under WITHOUT_COMPLEX. The module build ↵Mark Dickinson2009-10-152-4/+9
| | | | stage still fails.
* Issue #1754094: Improve the stack depth calculation in the compiler.Neil Schemenauer2009-10-141-12/+21
| | | | | There should be no other effect than a small decrease in memory use. Patch by Christopher Tur Lesniewski-Laas.
* #7050 fix a SystemError when using tuple unpacking and augmented assignmentBenjamin Peterson2009-10-031-0/+13
|
* Issue #7019: Unmarshalling of bad long data could produce unnormalizedMark Dickinson2009-09-291-3/+13
| | | | PyLongs. Raise ValueError instead.
* Fix issue #1590864, multiple threads and fork() can cause deadlocks, byThomas Wouters2009-09-161-19/+12
| | | | | | | | | | | | | | | | | | | | | | 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.
* revert unintended changesBenjamin Peterson2009-09-091-86/+8
|
* tabbifyBenjamin Peterson2009-09-091-8/+86
|
View Lorry Controller Status