| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Incorrect code was generated for:
foo(a = i for i in range(10))
This should have generated a SyntaxError. Fix the Grammar so
it raises a SyntaxError and test it.
I'm uncertain whether this should be backported. It makes
something that was Syntactically valid invalid. However,
the code would either be completely broken or do the wrong thing.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Will backport.
|
|
|
|
|
|
|
| |
Also provide a warning if a directory is passed on the command line.
Add minimal command line test.
Will backport.
|
|
|
|
|
|
|
| |
- 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.
|
|
|
|
|
|
| |
[ 1307978 ] Unsatisfied symbols: _PyGILState_NoteThreadState (code)
(note that this only happens in a threads-disabled build).
|
| |
|
|
|
|
| |
with an exception currently set!
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
evaluating keyword arguments.
|
|
|
|
|
| |
with IBM's 64-bit compiler (SF patch #1284289). This also closes SF
bug #105470: test_pwd fails on 64bit system (Opteron).
|
|
|
|
| |
Itanium2 with HP's 64-bit compiler (SF patch #1225212).
|
|
|
|
| |
sys.modules.
|
| |
|
|
|
|
| |
(fixes bug #1119418)
|
|
|
|
| |
Will backport to 2.4.
|
|
|
|
|
|
| |
Fix over-aggressive PyErr_Clear(). The same code fragment appears in
various guises in list.extend(), map(), filter(), zip(), and internally
in PySequence_Tuple().
|
| |
|
|
|
|
| |
hotshot.stats.load.
|
| |
|
|
|
|
|
| |
method still needs to support string exceptions, and allow None for the
third argument. Documentation updates are needed, too.
|
|
|
|
|
|
|
|
|
|
|
| |
- Handle both frozenset() and frozenset([]).
- Do not use singleton for frozenset subclasses.
- Finalize the singleton.
- Add test cases.
* Factor-out set_update_internal() from set_update(). Simplifies the
code for several internal callers.
* Factor constant expressions out of loop in set_merge_internal().
* Minor comment touch-ups.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
[ 1163563 ] Sub threads execute in restricted mode
basically by fixing bug 1010677 in a non-broken way.
Backport candidate.
|
|
|
|
|
| |
correspond to different interpreters (I hope, please revert if this is
wrong :).
|
|
|
|
|
|
|
|
| |
[ 1180997 ] lax error-checking in new-in-2.4 marshal stuff
which I'd assigned to Martin, but actually turned out to be easy to fix.
Also, a test.
|
|
|
|
|
|
| |
marshal_loads.
Bugfix candidate.
|
| |
|
|
|
|
|
|
|
|
|
| |
[ 1180995 ] binary formats for marshalling floats
Adds 2 new type codes for marshal (binary floats and binary complexes), a
new marshal version (2), updates MAGIC and fiddles the de-serializing of
code objects to be less likely to clobber the real reason for failing if
it fails.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[ 1181301 ] make float packing copy bytes when they can
which hasn't been reviewed, despite numerous threats to check it in
anyway if noone reviews it. Please read the diff on the checkin list,
at least!
The basic idea is to examine the bytes of some 'probe values' to see if
the current platform is a IEEE 754-ish platform, and if so
_PyFloat_{Pack,Unpack}{4,8} just copy bytes around.
The rest is hair for testing, and tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A problem regarding importing symlinked modules was recently reported on the
Cygwin mailing list:
http://cygwin.com/ml/cygwin/2005-04/msg00257.html
The following test case demonstrates the problem:
$ ls -l
total 1
lrwxrwxrwx 1 jt None 6 Apr 23 13:32 bar.py -> foo.py
-rw-r--r-- 1 jt None 24 Apr 18 20:13 foo.py
$ python -c 'import bar'
Traceback (most recent call last):
File "<string>", line 1, in ?
ImportError: No module named bar
Since Cygwin's case_ok() uses a modified version of the Windows's version, the
symlinked bar module actually resolves to file foo.py instead of bar.py. This
obviously causes the matching code to fail (regardless of case).
The patch fixes this problem by making Cygwin use the Mac OS X case_ok()
instead of a modified Window's version.
|
|
|
|
|
|
|
|
| |
[ 1176893 ] Readline segfault
by unsilly-ing PyGILState_Release().
Backport candidate.
|
|
|
|
|
| |
a default value of recursion limit from build systems. 1000 levels
are still too high for some 64bit systems.
|
|
|
|
|
| |
commit a yelp about a noted flaw the error messages for METH_KEYWORDS
functions under some circumstances.
|
|
|
|
| |
fixes the crash seen in bug #1165761
|
| |
|
|
|
|
| |
support for posix semaphores.
|
| |
|
|
|
|
| |
``class C(): pass`` is no longer a syntax error.
|
| |
|
|
|
|
|
| |
numbers in PyLong_AsLongLong, and update test suite accordingly.
Backported to 2.4.
|