summaryrefslogtreecommitdiffstats
path: root/Parser
Commit message (Collapse)AuthorAgeFilesLines
* Issue #25388: Fixed tokenizer crash when processing undecodable source codeSerhiy Storchaka2015-11-141-8/+6
| | | | with a null byte.
* do not call into python api if an exception is set (#24022)Benjamin Peterson2015-04-211-4/+3
|
* allow the keyword else immediately after (no space) an integer (closes #21642)Benjamin Peterson2014-06-071-5/+14
|
* Merge with 3.3Martin v. Löwis2014-02-281-2/+12
|\
| * Issue #20731: Properly position in source code files even if theyMartin v. Löwis2014-02-281-2/+12
| | | | | | | | are opened in text mode. Patch by Serhiy Storchaka.
* | merge 3.3 (#20588)Benjamin Peterson2014-02-111-2/+6
|\ \ | |/
| * don't put runtime values in array initializer for C89 compliance (closes #20588)Benjamin Peterson2014-02-111-2/+6
| |
* | Do not reset the line number because we already set file position to correctSerhiy Storchaka2014-01-091-8/+0
|\ \ | |/ | | | | | | | | value. (fixes error in patch for issue #18960)
| * Do not reset the line number because we already set file position to correctSerhiy Storchaka2014-01-091-8/+0
| | | | | | | | | | | | value. (fixes error in patch for issue #18960)
* | Issue #18960: Fix bugs with Python source code encoding in the second line.Serhiy Storchaka2014-01-091-4/+22
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * The first line of Python script could be executed twice when the source encoding (not equal to 'utf-8') was specified on the second line. * Now the source encoding declaration on the second line isn't effective if the first line contains anything except a comment. * As a consequence, 'python -x' works now again with files with the source encoding declarations specified on the second file, and can be used again to make Python batch files on Windows. * The tokenize module now ignore the source encoding declaration on the second line if the first line contains anything except a comment. * IDLE now ignores the source encoding declaration on the second line if the first line contains anything except a comment. * 2to3 and the findnocoding.py script now ignore the source encoding declaration on the second line if the first line contains anything except a comment.
| * Issue #18960: Fix bugs with Python source code encoding in the second line.Serhiy Storchaka2014-01-091-4/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * The first line of Python script could be executed twice when the source encoding (not equal to 'utf-8') was specified on the second line. * Now the source encoding declaration on the second line isn't effective if the first line contains anything except a comment. * As a consequence, 'python -x' works now again with files with the source encoding declarations specified on the second file, and can be used again to make Python batch files on Windows. * The tokenize module now ignore the source encoding declaration on the second line if the first line contains anything except a comment. * IDLE now ignores the source encoding declaration on the second line if the first line contains anything except a comment. * 2to3 and the findnocoding.py script now ignore the source encoding declaration on the second line if the first line contains anything except a comment.
* | Issue #16136: Remove VMS support and VMS-related codeChristian Heimes2013-12-211-8/+0
| |
* | upcast int to size_t to silence two ↵Christian Heimes2013-12-041-1/+1
| | | | | | | | autological-constant-out-of-range-compare warnings with clang.
* | Fix a compiler warning on Windows 64-bit in parsetok.cVictor Stinner2013-11-181-1/+2
| | | | | | | | Python parser doesn't support lines longer than INT_MAX bytes yet
* | Fix compiler warnings on Windows 64-bit in grammar.cVictor Stinner2013-11-181-2/+2
| | | | | | | | INT_MAX states and labels should be enough for everyone
* | Issue #1772673: The type of `char*` arguments now changed to `const char*`.Serhiy Storchaka2013-10-197-21/+25
| |
* | Issue #16742: My fix on PyOS_StdioReadline() was incomplete, PyMem_FREE() wasVictor Stinner2013-10-191-3/+3
| | | | | | | | not patched
* | Issue #4555: All exported C symbols are now prefixed with either "Py" or "_Py".Antoine Pitrou2013-10-121-2/+2
| | | | | | | | ("make smelly" now clean)
* | Close #16742: Fix misuse of memory allocations in PyOS_Readline()Victor Stinner2013-10-101-6/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GIL must be held to call PyMem_Malloc(), whereas PyOS_Readline() releases the GIL to read input. The result of the C callback PyOS_ReadlineFunctionPointer must now be a string allocated by PyMem_RawMalloc() or PyMem_RawRealloc() (or NULL if an error occurred), instead of a string allocated by PyMem_Malloc() or PyMem_Realloc(). Fixing this issue was required to setup a hook on PyMem_Malloc(), for example using the tracemalloc module. PyOS_Readline() copies the result of PyOS_ReadlineFunctionPointer() into a new buffer allocated by PyMem_Malloc(). So the public API of PyOS_Readline() does not change.
* | Move open outside try/finallyEli Bendersky2013-09-261-1/+1
| |
* | Don't use fancy new Python features like 'with' - some bots don't have themEli Bendersky2013-09-261-1/+4
| | | | | | | | and can't bootstrap the parser.
* | Normalize whitespaceEli Bendersky2013-09-261-1/+1
| |
* | Small fixes in Parser/asdl.py - no change in functionality.Eli Bendersky2013-09-261-4/+6
| | | | | | | | | | | | 1. Make it work when invoked directly from the command-line. It was failing due to a couple of stale function/class usages in the __main__ section. 2. Close the parsed file in the parse() function after opening it.
* | Issue #18571: Implementation of the PEP 446: file descriptors and file handlesVictor Stinner2013-08-271-0/+5
| | | | | | | | | | are now created non-inheritable; add functions os.get/set_inheritable(), os.get/set_handle_inheritable() and socket.socket.get/set_inheritable().
* | Close #11619: The parser and the import machinery do not encode UnicodeVictor Stinner2013-08-261-14/+65
| | | | | | | | filenames anymore on Windows.
* | #18803: merge with 3.3.Ezio Melotti2013-08-251-1/+1
|\ \ | |/
| * #18803: fix more typos. Patch by Févry Thibault.Ezio Melotti2013-08-251-1/+1
| |
* | Issue #18722: Remove uses of the "register" keyword in C code.Antoine Pitrou2013-08-134-27/+27
| |
* | Issue #18368: PyOS_StdioReadline() no longer leaks memory when realloc() fails.Christian Heimes2013-08-061-5/+17
|\ \ | |/
| * Issue #18368: PyOS_StdioReadline() no longer leaks memory when realloc() fails.Christian Heimes2013-08-061-5/+17
| |
* | Silence warning about set but unused variable inside compile_atom() in ↵Christian Heimes2013-07-311-0/+1
|\ \ | |/ | | | | non-debug builds
| * Silence warning about set but unused variable inside compile_atom() in ↵Christian Heimes2013-07-311-0/+1
| | | | | | | | non-debug builds
* | Issue #18552: Check return value of PyArena_AddPyObject() in obj2ast_object().Christian Heimes2013-07-261-3/+7
|\ \ | |/
| * Issue #18552: Check return value of PyArena_AddPyObject() in obj2ast_object().Christian Heimes2013-07-261-3/+7
| |
* | (Merge 3.3) Parser/asdl_c.py: use Py_CLEAR()Victor Stinner2013-07-261-2/+1
|\ \ | |/
| * Parser/asdl_c.py: use Py_CLEAR()Victor Stinner2013-07-261-2/+1
| |
* | (Merge 3.3) According to the PEP 7, C code must "use 4-space indents"Victor Stinner2013-07-261-1/+1
|\ \ | |/ | | | | Replace 8 spaces with 4.
| * According to the PEP 7, C code must "use 4-space indents"Victor Stinner2013-07-261-1/+1
| | | | | | | | Replace 8 spaces with 4.
* | Some compilers complain about 'control reaches end of non-void function'Christian Heimes2013-07-221-0/+1
|\ \ | |/ | | | | because they don't understand that Py_FatalError() terminates the program.
| * Some compilers complain about 'control reaches end of non-void function'Christian Heimes2013-07-221-0/+1
| | | | | | | | because they don't understand that Py_FatalError() terminates the program.
* | Add sanity check to PyGrammar_LabelRepr() in order to catch invalid tokens ↵Christian Heimes2013-07-221-1/+4
|\ \ | |/ | | | | | | | | | | when debugging a new grammar. CID 715360
| * Add sanity check to PyGrammar_LabelRepr() in order to catch invalid tokens ↵Christian Heimes2013-07-221-1/+4
| | | | | | | | | | | | | | when debugging a new grammar. CID 715360
* | Issue #18408: Fix Python-ast.c: handle init_types() failure (ex: MemoryError)Victor Stinner2013-07-161-3/+6
| |
* | merge 3.3Benjamin Peterson2013-07-161-1/+2
|\ \ | |/
| * move declaration to top of blockBenjamin Peterson2013-07-161-1/+2
| |
* | merge 3.3 (closes #18470)Benjamin Peterson2013-07-161-36/+46
|\ \ | |/
| * check the return value of new_string() (closes #18470)Benjamin Peterson2013-07-161-36/+46
| |
* | Issue #18408: parsetok() must not write into stderr on memory allocation errorVictor Stinner2013-07-111-1/+0
| | | | | | | | The caller gets an error code and can raise a classic Python exception.
* | Issue #18408: parsetok() must not write into stderr on memory allocation errorVictor Stinner2013-07-111-1/+0
| | | | | | | | The caller gets an error code and can raise a classic Python exception.
* | Fix resource leak in parser, free node ptrChristian Heimes2013-06-291-0/+1
| | | | | | | | | | CID 1028068 (#1 of 1): Resource leak (RESOURCE_LEAK) leaked_storage: Variable n going out of scope leaks the storage it points to.