Raymond Hettinger
07359a7fed
Document how the pattern recognizer keeps all of its references in bounds.
...
Add a test in case the underlying assumptions ever change (i.e. the
compiler starts generating code blocks that are not punctuated by
RETURN_VALUE).
2005-02-21 20:03:14 +00:00
Raymond Hettinger
80121491e0
Teach the peepholer to fold unary operations on constants.
...
Afterwards, -0.5 loads in a single step and no longer requires a runtime
UNARY_NEGATIVE operation.
2005-02-20 12:41:32 +00:00
Raymond Hettinger
b615bf0681
Remove the set conversion which didn't work with: [] in (0,)
2005-02-10 01:42:32 +00:00
Raymond Hettinger
5e547969f8
Have set conversion replace existing constant if not used elsewhere.
2005-02-09 21:24:51 +00:00
Guido van Rossum
0f1f63cf07
Close the discussion in SF bug 1069160.
2005-02-08 02:07:57 +00:00
Raymond Hettinger
7fcb7869ba
Adopt Skip's idea to optimize lists of constants in the context
...
of a "in" or "not in" test.
2005-02-07 19:32:38 +00:00
Raymond Hettinger
a164574937
Transform "x in (1,2,3)" to "x in frozenset([1,2,3])".
...
Inspired by Skip's idea to recognize the throw-away nature of sequences
in this context and to transform their type to one with better performance.
2005-02-06 22:05:42 +00:00
Jeremy Hylton
c9add9a483
Fix bug that allowed future statements virtually anywhere in a module.
...
If we exit via the break here, we need to set ff_last_lineno or
FUTURE_POSSIBLE() will remain true. The bug affected statements
containing a variety of expressions, but not all expressions. It has
been present since Python 2.2.
2005-02-04 18:38:43 +00:00
Martin v. Löwis
13a1fde4da
Partially revert #1074011 ; don't try to fflush stdin.
...
Backported to 2.3 and 2.4.
2005-01-27 18:56:16 +00:00
Raymond Hettinger
9feb267caf
Do not fold a constant if a large sequence will result.
...
Saves space in the presence of code like: (None,)*10000
2005-01-26 12:50:05 +00:00
Anthony Baxter
c560a00966
happy new year! (on the trunk)
2005-01-25 12:40:01 +00:00
Martin v. Löwis
8e3ca8af26
Flush std{in,out,err} before closing it. Fixes #1074011 .
...
Will backport to 2.4 and 2.3.
2005-01-23 09:41:49 +00:00
Michael W. Hudson
75eabd2944
Change the name of the macro used by --with-tsc builds to the less
...
inscrutable READ_TIMESTAMP.
2005-01-18 15:56:11 +00:00
Michael W. Hudson
969f485cba
-X died some time ago; remove a tiny bit of associated cruft.
2005-01-18 15:26:11 +00:00
Andrew MacIntyre
2bea474476
make thread stack size compile-time tunable on OS/2
2005-01-17 12:16:36 +00:00
Fred Drake
d7c27bef52
remove unused variable
2005-01-12 16:00:55 +00:00
Raymond Hettinger
a422c34b70
SF 1098985: set objects cannot be marshalled
2005-01-11 03:03:27 +00:00
Skip Montanaro
c9a4762bd6
comment tweak
2005-01-08 21:58:58 +00:00
Armin Rigo
664b43b3f4
Re-running python with/without the -Qnew flag uses incorrectly optimized
...
bytecodes from the previously saved .pyc files. Fixed by disabling the static
optimization of BINARY_DIVIDE between two constants.
2005-01-07 18:10:51 +00:00
Raymond Hettinger
c34f8673a1
Teach the peephole optimizer to fold simple constant expressions.
2005-01-02 06:17:33 +00:00
Armin Rigo
2ccea17856
Any call to marshal.dumps() with the new optional argument 'version' just
...
immediately segfaults, due to a typo! This was obviously never tested...
Added a test for it, and also fixed the documentation.
2004-12-20 12:25:57 +00:00
Brett Cannon
9e635cf3ae
Put parentheses around the assignment in the 'while' loop conditional
...
expression in min_max() to shut gcc up.
2004-12-07 00:25:35 +00:00
Raymond Hettinger
3b0c7c20a1
SF patch #1077353 : add key= argument to min and max
...
(First draft of patch contributed by Steven Bethard.)
2004-12-03 08:30:39 +00:00
Kurt B. Kaiser
4c79a83e0c
Hye-Shik Chang's fix for Bug 875692.
...
Improve signal handling, especially when using threads, by forcing an early
re-execution of PyEval_EvalFrame() "periodic" code when things_to_do is not
cleared by Py_MakePendingCalls().
M Misc/NEWS
M Python/ceval.c
2004-11-23 18:06:08 +00:00
Tim Peters
fb1ffb0ebb
SF bug 1061968: threads: segfault or Py_FatalError at exit
...
PyGILState_Ensure(): The fix in 2.4a3 for bug 1010677 reintroduced thread
shutdown race bug 225673. Repaired by (once again) ensuring the GIL is
held whenever deleting a thread state.
Alas, there's no useful test case for this shy bug. Four years ago, only
Guido could provoke it, on his box, and today only Armin can provoke it
on his box. I've never been able to provoke it (but not for lack of
trying!).
This is a critical fix for 2.3.5 too, since the fix for 1010677 got
backported there already and so also reintroduced 225673. I don't intend to
backport this fix. For whoever (if anyone) does, there are other thread
fixes in 2.4 that need backporting too, and I bet they need to happen first
for this patch to apply cleanly.
2004-11-08 04:30:21 +00:00
