summaryrefslogtreecommitdiffstats
path: root/Python/ast.c
Commit message (Collapse)AuthorAgeFilesLines
* Issue #3360: Fix incorrect parsing of "020000000000.0".Mark Dickinson2008-07-161-10/+1
|
* #3219 repeated keyword arguments aren't allowed in function calls anymoreBenjamin Peterson2008-07-011-0/+10
|
* Merge in release25-maint r60793:Gregory P. Smith2008-06-111-0/+3
| | | | | | Added checks for integer overflows, contributed by Google. Some are only available if asserts are left in the code, in cases where they can't be triggered from Python code.
* This reverts r63675 based on the discussion in this thread:Gregory P. Smith2008-06-091-14/+14
| | | | | | | http://mail.python.org/pipermail/python-dev/2008-June/079988.html Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names in the spirit of 3.0 are available via a #define only. See the email thread.
* warn about parameter tuple unpackingBenjamin Peterson2008-06-081-0/+3
|
* Warn about assigning to Py3k keywords (True and False)Benjamin Peterson2008-06-081-33/+27
|
* add an ast_warn helper function to make adding those Py3k warnings easierBenjamin Peterson2008-06-081-7/+15
|
* change Py3k backquote warning to a SyntaxWarning and add a testBenjamin Peterson2008-06-081-1/+1
|
* Renamed PyString to PyBytesChristian Heimes2008-05-261-18/+18
|
* The compiling struct is now passed around to all AST helpers (see issue 2720)Benjamin Peterson2008-05-031-32/+32
|
* Patch #2511: Give the "excepthandler" AST item proper attributes by making ↵Georg Brandl2008-03-301-3/+3
| | | | it a Sum.
* Patch #2477: Added from __future__ import unicode_literalsChristian Heimes2008-03-261-11/+14
| | | | The new PyParser_*Ex() functions are based on Neal's suggestion and initial patch. The new __future__ feature makes all '' and r'' unicode strings. b'' and br'' stay (byte) strings.
* Make Py3k warnings consistent w.r.t. punctuation; also respect theGeorg Brandl2008-03-251-1/+1
| | | | EOL 80 limit and supply more alternatives in warning messages.
* Issue #2400: Allow relative imports to "import *".Martin v. Löwis2008-03-191-4/+0
|
* Issue#2238: some syntax errors from *args or **kwargs expressionsAmaury Forgeot d'Arc2008-03-051-0/+4
| | | | | | | | | | | | | | would give bogus error messages, because of untested exceptions:: >>> f(**g(1=2)) XXX undetected error Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: 'int' object is not iterable instead of the expected SyntaxError: keyword can't be an expression Will backport.
* Patch #1759: Backport of PEP 3129 class decoratorsChristian Heimes2008-02-231-24/+46
| | | | with some help from Georg
* Added bytes and b'' as aliases for str and ''Christian Heimes2008-01-181-0/+3
|
* Make Python compile with --disable-unicode.Georg Brandl2008-01-071-0/+2
|
* Added filename to compiling struct based on Martin's suggestion.Christian Heimes2007-11-241-1/+3
| | | | I'm wonder why I was trying to add the filename to the node all the time. The compiling struct is more obvious.
* And yet another fix for the patch. Paul Moore has send me a note that I've ↵Christian Heimes2007-11-231-8/+9
| | | | missed a declaration. The additional code has moved the declaration in the middle of the block.
* How did the comment get there?Christian Heimes2007-11-231-1/+1
|
* Fixed problems in the last commit. Filenames and line numbers weren't ↵Christian Heimes2007-11-231-4/+8
| | | | | | reported correctly. Backquotes still don't report the correct file. The AST nodes only contain the line number but not the file name.
* Applied patch #1754273 and #1754271 from Thomas GleeChristian Heimes2007-11-231-0/+4
| | | | The patches are adding deprecation warnings for back ticks and <>
* Fix Coverity #158: Check the correct variable.Neal Norwitz2007-10-051-1/+1
|
* Place #ifdef Py_USING_UNICODE around decode_unicode().Georg Brandl2007-08-061-0/+2
|
* SF patch# 1755885 by Kurt Kaiser: show location of Unicode escape errors.Guido van Rossum2007-07-181-2/+19
| | | | (Slightly tweaked for style and refcounts.)
* Disallow function calls like foo(None=1).Georg Brandl2007-06-071-0/+4
| | | | Backport from py3k rev. 55708 by Guido.
* Backport PEP 3110's new 'except' syntax to 2.6.Collin Winter2007-05-181-1/+1
|
* Handle a couple of uncaught errors. This should be backportedNeal Norwitz2007-05-031-0/+4
|
* Actually raise an exception before calling ast_error_finish.Georg Brandl2007-05-021-0/+2
| | | | Triggers an assertion otherwise.
* Clean up formatting of this file.Jeremy Hylton2007-03-161-2029/+2048
| | | | | | | | | | The file should now follow PEP 7, except that it uses 4 space indents (in the style of Py3k). This particular code would be really hard to read with the regular tab idents. Other changes: - reflow long lines - change multi-line conditionals to have test at end of line
* Patch #1642547: Fix an error/crash when encountering syntax errors in ↵Collin Winter2007-03-161-14/+26
| | | | | | complex if statements. Will backport.
* tabifyJeremy Hylton2007-02-271-2005/+2005
| | | | | Note that ast.c still has a mix of tabs and spaces, because it attempts to use four-space indents for more of the new code.
* Bug #1588287: fix invalid assertion for `1,2` in debug builds.Neal Norwitz2006-11-041-0/+1
| | | | Will backport
* Bug #1557232: fix seg fault with def f((((x)))) and def f(((x),)).Neal Norwitz2006-09-221-2/+24
| | | | | | | These tests should be improved. Hopefully this fixes variations when flipping back and forth between fpdef and fplist. Backport candidate.
* with and as are now keywords. There are some generated files I can't recreate.Neal Norwitz2006-09-061-12/+0
|
* M-x untabifyNeal Norwitz2006-09-051-821/+821
|
* Add a comment about some refactoring. (There's probably more that should be ↵Neal Norwitz2006-09-051-6/+5
| | | | done.) I will reformat this file in the next checkin due to the inconsistent tabs/spaces.
* Bug #1520864 (again): unpacking singleton tuples in list comprehensions andNeal Norwitz2006-09-051-4/+12
| | | | | | | | | | | | | generator expressions (x for x, in ... ) works again. Sigh, I only fixed for loops the first time, not list comps and genexprs too. I couldn't find any more unpacking cases where there is a similar bug lurking. This code should be refactored to eliminate the duplication. I'm sure the listcomp/genexpr code can be refactored. I'm not sure if the for loop can re-use any of the same code though. Will backport to 2.5 (the only place it matters).
* Klocwork made another run and found a bunch more problems.Neal Norwitz2006-08-121-0/+2
| | | | | | | This is the first batch of fixes that should be easy to verify based on context. This fixes problem numbers: 220 (ast), 323-324 (symtable), 321-322 (structseq), 215 (array), 210 (hotshot), 182 (codecs), 209 (etree).
* Add some asserts and update commentsNeal Norwitz2006-07-301-2/+3
|
* Patch #1531113: Fix augmented assignment with yield expressions.Neal Norwitz2006-07-301-7/+9
| | | | Also fix a SystemError when trying to assign to yield expressions.
* Handle more memory allocation failures without crashing.Neal Norwitz2006-07-211-2/+4
|
* Bug #1520864: unpacking singleton tuples in for loop (for x, in) work again.Neal Norwitz2006-07-121-2/+6
|
* Fix SF bug 1441486: bad unary minus folding in compiler.Neil Schemenauer2006-07-091-20/+53
|
* Fix AST compiler bug #1501934: incorrect LOAD/STORE_GLOBAL generation.Neil Schemenauer2006-07-091-2/+3
|
* Fix SF bug #1519018: 'as' is now validated properly in import statementsNeal Norwitz2006-07-081-1/+12
|
* Replace Py_BuildValue("OO") by PyTuple_Pack.Georg Brandl2006-05-261-1/+1
|
* Fix #1474677, non-keyword argument following keyword.Neal Norwitz2006-05-191-0/+5
|
* - Bug #1487966: Fix SystemError with conditional expression in assignmentNeal Norwitz2006-05-151-0/+3
| | | | Most of the test_syntax changes are just updating the numbers.
generated by cgit v0.12 at 2024-10-23 10:20:52 (GMT)