| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Expand set of errors caught in set_context(). Some new errors, some
old error messages changed for consistency.
Fixed error checking in generator expression code. The first set of
tests were impossible condition given the grammar. In general, the
ast code uses REQ() for those sanity checks.
Fix some error handling for augmented assignments. As comments in the
code explain, set_context() ought to work here, but I got unexpected
crashes when I tried it. Should come back to this.
Add note to Grammar that yield expression is a special case.
Add doctest cases for SyntaxErrors raised by ast.c.
|
|
|
|
| |
non-debug builds, but is used in debug builds
|
|
|
|
|
| |
for 2 different values without changing. I think this was the intent.
The unused warning only occurs when not building in debug mode.
|
| |
|
|
|
|
| |
Most of these can be backported.
|
|
|
|
| |
Needs backport.
|
|
|
|
| |
simplifies a lot of error handling code, and fixes many memory leaks.
|
|
|
|
|
|
|
| |
comment based on 'sys.args[0]' does not depend on the path. For Python
builds from a remote directory ("/path/to/configure; make") the previous
logic used to include the "/path/to" portion in Python-ast.h. Then svn
would consider this file to be locally modified.
|
|
|
|
|
|
|
|
| |
Strip off leading dots and slash so the generated files are the same regardless
of whether you configure in the checkout directory or build.
If anyone configures in a different directory, we might want a cleaner
approach using os.path.*(). Hopefully this is good enough.
|
|
|
|
|
|
| |
Call error_ret() in decode_str(). It was called in some other places,
but seemed inconsistent. It is safe to call PyTokenizer_Free() after
calling error_ret().
|
| |
|
| |
|
|
|
|
| |
a bunch of names
|
| |
|
|
|
|
| |
properties now.
|
|
|
|
| |
Get rid of "int i" unused warnings from Python-ast.c which we are generating.
|
|
|
|
| |
backport candidate
|
|
|
|
|
|
|
|
|
|
| |
This change implements a new bytecode compiler, based on a
transformation of the parse tree to an abstract syntax defined in
Parser/Python.asdl.
The compiler implementation is not complete, but it is in stable
enough shape to run the entire test suite excepting two disabled
tests.
|
|
|
|
|
|
|
| |
- SF Bug #772896, unknown encoding results in MemoryError, which is not helpful
I will only backport the segfault fix. I'll let Anthony decide if he wants
the other changes backported. I will do the backport if asked.
|
|
|
|
| |
with a PEP 263 encoding declaration results in long decoded line.
|
|
|
|
|
|
|
|
|
| |
because (essentially) I didn't realise that PY_BEGIN/END_ALLOW_THREADS
actually expanded to nothing under a no-threads build, so if you somehow
NULLed out the threadstate (e.g. by calling PyThread_SaveThread) it would
stay NULLed when you return to Python. Argh!
Backport candidate.
|
| |
|
|
|
|
| |
a few remaining calls to signal() were converted to PyOS_setsig().
|
|
|
|
|
|
|
| |
modes like non-interactive modes. This allows for non-latin-1 users
to write unicode strings directly and sets Japanese users free from
weird manual escaping <wink> in shift_jis environments.
(Reviewed by Martin v. Loewis)
|
|
|
|
|
| |
"@ seems the syntax that everybody can hate equally"
Implementation by Mark Russell, from SF #979728.
|
|
|
|
| |
[ 987287 ] Python 2.4a1, interpreter hanging on Keyboard Interrupt
|
| |
|
|
|
|
| |
isn't always set to an integer value when it's defined.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[ 960406 ] unblock signals in threads
although the changes do not correspond exactly to any patch attached to
that report.
Non-main threads no longer have all signals masked.
A different interface to readline is used.
The handling of signals inside calls to PyOS_Readline is now rather
different.
These changes are all a bit scary! Review and cross-platform testing
much appreciated.
|
| |
|
|
|
|
|
| |
Change %08l to %p to print a pointer.
Will backport to 2.3.
|
| |
|
|
|
|
| |
mid 1990. Remove an untrue XXX comment.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
A change from Duncan Booth, to deal with changes in the way pgen gets
built. Note that graminit.[ch] aren't normally built on Windows (they're
obtained from CVS).
|
|
|
|
| |
riscospath.extsep, and use os.extsep throughout.
|
| |
|
| |
|
|
|
|
|
|
| |
work. This includes some more code that used to be part of pgen in
the main parser; I'm okay with that. I'll see if the Windows build
needs work next.
|
|
|
|
|
|
| |
the build, so I'm restoring it. I'm not sure what Neal's intent was,
since the line following the one he removed was "REQN(i, 1)" so i is
obviously used. ;)
|
| |
|
|
|
|
|
|
| |
Remove the usage of PyErr_WarnExplicit() since this could cause
sensitive information from the source files to appear in e.g.
log files.
|
|
|
|
|
|
|
|
|
| |
with an indented code block but no newline would raise SyntaxError.
This would have been a four-line change in parsetok.c... Except
codeop.py depends on this behavior, so a compilation flag had to be
invented that causes the tokenizer to revert to the old behavior;
this required extra changes to 2 .h files, 2 .c files, and 2 .py
files. (Fixes SF bug #501622.)
|
|
|
|
| |
mark. Added unit test.
|
|
|
|
|
| |
Ensure that the 'size' arg is correctly passed to the encoding reader to
prevent buffer overflows.
|
| |
|
|
|
|
| |
Cast param to isalnum() to int.
|
|
|
|
|
|
| |
(see Patch 512981). I changed stdin to sys_stdin in the body of the
function, but did not change stderr to sys_stdout, though I suspect that may
be the correct course. I don't know the code involved well enough to judge.
|