summaryrefslogtreecommitdiffstats
path: root/Python
Commit message (Collapse)AuthorAgeFilesLines
* remove error checks already done in set_context()Benjamin Peterson2009-06-081-25/+0
|
* remove useless assertionBenjamin Peterson2009-06-081-1/+0
|
* Issue #5330: C functions called with keyword arguments were not reported byAntoine Pitrou2009-05-301-2/+16
| | | | the various profiling modules (profile, cProfile). Patch by Hagen Fürstenau.
* Fix nearly all compilation warnings under Apple gcc-4.0. Tested with OPT="-gJeffrey Yasskin2009-05-291-12/+0
| | | | | | -Wall -Wstrict-prototypes -Werror" in both --with-pydebug mode and --without. There's still a batch of non-prototype warnings in Xlib.h that I don't know how to fix.
* further hint to where the open docs really arePhilip Jenvey2009-05-281-1/+1
|
* teach the peepholer about SETUP_WITHBenjamin Peterson2009-05-261-0/+3
|
* Allow multiple context managers in one with statement, as proposedGeorg Brandl2009-05-252-39/+61
| | | | | | | in http://codereview.appspot.com/53094 and accepted by Guido. The construct is transformed into multiple With AST nodes so that there should be no problems with the semantics.
* take into account the fact that SETUP_WITH pushes a finally blockBenjamin Peterson2009-05-251-1/+1
|
* add a SETUP_WITH opcodeBenjamin Peterson2009-05-253-57/+57
| | | | | It speeds up the with statement and correctly looks up the special methods involved.
* handle errors from _PyObject_LookupSpecial when __get__ failsBenjamin Peterson2009-05-251-4/+6
|
* Issue #6042:Jeffrey Yasskin2009-05-232-65/+14
| | | | | | | | | | | | | | | lnotab-based tracing is very complicated and isn't documented very well. There were at least 3 comment blocks purporting to document co_lnotab, and none did a very good job. This patch unifies them into Objects/lnotab_notes.txt which tries to completely capture the current state of affairs. I also discovered that we've attached 2 layers of patches to the basic tracing scheme. The first layer avoids jumping to instructions that don't start a line, to avoid problems in if statements and while loops. The second layer discovered that jumps backward do need to trace at instructions that don't start a line, so it added extra lnotab entries for 'while' and 'for' loops, and added a special case for backward jumps within the same line. I replaced these patches by just treating forward and backward jumps differently.
* support building with subversion 1.7 #6094Benjamin Peterson2009-05-231-1/+1
|
* Issue #3527: Removed Py_WIN_WIDE_FILENAMES which is not used any more.Hirokazu Yamamoto2009-05-171-6/+2
|
* Move news item to correct section, remove spurious 'see below'R. David Murray2009-05-131-1/+1
| | | | from docstring.
* Issue 5994: add docstrings to marshal.R. David Murray2009-05-131-5/+81
|
* don't ignore exceptions from _PyObject_LengthHintBenjamin Peterson2009-05-091-1/+3
|
* convert some more special methods to use _PyObject_LookupSpecialBenjamin Peterson2009-05-091-12/+7
|
* Issue 5954, PyFrame_GetLineNumber:Jeffrey Yasskin2009-05-083-4/+3
| | | | | | | | | | | | | | Most uses of PyCode_Addr2Line (http://www.google.com/codesearch?q=PyCode_Addr2Line) are just trying to get the line number of a specified frame, but there's no way to do that directly. Forcing people to go through the code object makes them know more about the guts of the interpreter than they should need. The remaining uses of PyCode_Addr2Line seem to be getting the line from a traceback (for example, http://www.google.com/codesearch/p?hl=en#u_9_nDrchrw/pygame-1.7.1release/src/base.c&q=PyCode_Addr2Line), which is replaced by the tb_lineno field. So we may be able to deprecate PyCode_Addr2Line entirely for external use.
* Issue #5920: Changed format.__float__ and complex.__float__ to use a ↵Eric Smith2009-05-051-7/+6
| | | | precision of 12 when using the empty presentation type. This more closely matches str()'s behavior and reduces surprises when adding alignment flags to an empty format string. Patch by Mark Dickinson.
* Don't use PyOS_strnicmp for NaN and Inf detection: it's locale-aware.Mark Dickinson2009-05-031-3/+16
|
* Eliminate some locale-dependent calls to isspace and tolower.Mark Dickinson2009-05-031-1/+1
|
* Issue #1588: Add complex.__format__.Eric Smith2009-04-302-7/+8
|
* Remove format_float and use _PyOS_double_to_string instead.Mark Dickinson2009-04-291-0/+14
|
* Issue #5864: format(1234.5, '.4') gives misleading resultMark Dickinson2009-04-291-11/+104
| | | | (Backport of r72109 from py3k.)
* Silence warning on Windows.Eric Smith2009-04-281-1/+1
|
* Issue #5793: rationalize isdigit / isalpha / tolower, etc. Will port to ↵Eric Smith2009-04-272-15/+223
| | | | py3k. Should fix Windows buildbot errors.
* Fix typo in function nameMark Dickinson2009-04-261-3/+3
|
* Backport r71967 changes from py3k to trunk.Mark Dickinson2009-04-261-30/+57
| | | | (Internal plumbing changes for float parsing.)
* Issue #5835, deprecate PyOS_ascii_formatd.Eric Smith2009-04-251-45/+109
| | | | | | If anyone wants to clean up the documentation, feel free. It's my first documentation foray, and it's not that great. Will port to py3k with a different strategy.
* Issue #5816:Mark Dickinson2009-04-241-2/+3
| | | | | | | | - simplify parsing and printing of complex numbers - make complex(repr(z)) round-tripping work for complex numbers involving nans, infs, or negative zeros - don't accept some of the stranger complex strings that were previously allowed---e.g., complex('1..1j')
* Backport of some of the work in r71665 to trunk. This reworks much ofEric Smith2009-04-221-57/+130
| | | | | | | | | | | | | | | | | | | | | int, long, and float __format__(), and it keeps their implementation in sync with py3k. Also added PyOS_double_to_string. This is the "fallback" version that's also available in trunk, and should be kept in sync with that code. I'll add an issue to document PyOS_double_to_string in the C API. There are many internal cleanups. Externally visible changes include: - Implement PEP 378, Format Specifier for Thousands Separator, for floats, ints, and longs. - Issue #5515: 'n' formatting for ints, longs, and floats handles leading zero formatting poorly. - Issue #5772: For float.__format__, don't add a trailing ".0" if we're using no type code and we have an exponent.
* Issue #1869: Fix a couple of minor round() issues.Mark Dickinson2009-04-181-4/+1
|
* Backport r71704 (add configure check for C99 round function) to trunk.Mark Dickinson2009-04-181-0/+13
|
* copysign shouldn't be declared as static in pymath.cMark Dickinson2009-04-181-1/+1
|
* #5580: no need to use parentheses when converterr() argument is actually a ↵Georg Brandl2009-04-051-1/+1
| | | | type description.
* - Issue #3845: In PyRun_SimpleFileExFlags avoid invalid memory access withMatthias Klose2009-04-041-2/+3
| | | | short file names.
* Issue #2396: backport the memoryview object.Antoine Pitrou2009-04-021-1/+1
|
* PyErr_NormalizeException may not set an error, so convert the PyErr_SetObjectGeorg Brandl2009-04-021-1/+9
| | | | call on hitting the recursion limit into just assigning it to the arguments provided.
* Fix two issues introduced by issue #71031 by changing the signature ofBrett Cannon2009-04-021-1/+1
| | | | PyImport_AppendInittab() to take a const char *.
* PyImport_AppendInittab() took a char * as a first argument even though thatBrett Cannon2009-04-021-1/+1
| | | | | | | string was stored beyond the life of the call. Changed the signature to be const char * to help make this point. Closes issue #1419652.
* fix error handlingBenjamin Peterson2009-04-021-4/+7
|
* In PyErr_GivenExceptionMatches, temporarily bump the recursionGeorg Brandl2009-04-021-1/+7
| | | | | limit, so that in the most common case PyObject_IsSubclass will not raise a recursion error we have to ignore anyway.
* _warnings was importing itself to get an attribute. That's bad if warnings getsBrett Cannon2009-04-011-16/+30
| | | | | | called in a thread that was spawned by an import itself. Last part to close #1665206.
* Issue 5619: Pass MS CRT debug flags into subprocessesJesse Noller2009-03-311-0/+2
|
* Add check for PyDict_Update() error.Jeremy Hylton2009-03-311-1/+2
|
* Global statements from one function leaked into parallel functions.Jeremy Hylton2009-03-311-22/+101
| | | | | | | | | | | | | Re http://bugs.python.org/issue4315 The symbol table used the same name dictionaries to recursively analyze each of its child blocks, even though the dictionaries are modified during analysis. The fix is to create new temporary dictionaries via the analyze_child_block(). The only information that needs to propagate back up is the names of the free variables. Add more comments and break out a helper function. This code doesn't get any easier to understand when you only look at it once a year.
* Issue #4258: Use 30-bit digits for Python longs, on 64-bit platforms.Mark Dickinson2009-03-203-39/+112
| | | | Backport of r70459.
* fix strange errors when setting attributes on tracebacks #4034Benjamin Peterson2009-03-181-14/+8
|
* Make marshalling errors a little more informative as to what went wrongNick Coghlan2009-03-151-13/+13
|
* Require implementations for warnings.showwarning() support the 'line' argument.Brett Cannon2009-03-111-49/+17
| | | | | | Was a DeprecationWarning for not supporting it since Python 2.6. Closes issue #3652.
generated by cgit v0.12 at 2024-10-23 23:23:40 (GMT)