Benjamin Peterson
bea424af98
more _PyString_Resize error checking
2010-04-03 00:57:33 +00:00
Antoine Pitrou
76c8649038
Issue #8276 : PyEval_CallObject() is now only available in macro form. The
...
function declaration, which was kept for backwards compatibility reasons,
is now removed (the macro was introduced in 1997!).
2010-04-01 16:42:11 +00:00
Benjamin Peterson
06638735fc
make naming convention consistent
2010-03-25 23:27:16 +00:00
Larry Hastings
402b73fb8d
Backported PyCapsule from 3.1, and converted most uses of
...
CObject to PyCapsule.
2010-03-25 00:54:54 +00:00
Benjamin Peterson
bb9d726357
take into account keyword arguments when passing too many args
2010-03-21 20:30:30 +00:00
Benjamin Peterson
965458931f
improve error message from passing inadequate number of keyword arguments #6474
...
Note this removes the "non-keyword" or "keyword" phrases from these messages.
2010-03-21 20:21:00 +00:00
Benjamin Peterson
88e7ebac4c
co_varnames is certainly a tuple, so let's not waste time finding out
2010-03-21 19:39:52 +00:00
Benjamin Peterson
d51b259b31
remove pointless condition
2010-03-21 19:35:39 +00:00
Benjamin Peterson
56472c2463
flatten condition
2010-03-21 19:24:08 +00:00
Benjamin Peterson
0dee9c1b5c
prevent lambda functions from having docstrings #8164
2010-03-17 20:41:42 +00:00
Mark Dickinson
f1ff88f0e4
Fix incorrect error checks in structmember.c (backport of r78920 from py3k).
2010-03-13 14:18:34 +00:00
Victor Stinner
6664426d7c
Issue #3137 : Don't ignore errors at startup, especially a keyboard interrupt
...
(SIGINT). If an error occurs while importing the site module, the error is
printed and Python exits. Initialize the GIL before importing the site
module.
2010-03-10 22:30:19 +00:00
Benjamin Peterson
9c4742e6ce
more specific exception for wrong kind of raise #8082
2010-03-07 00:00:37 +00:00
Victor Stinner
71fb87e64c
Issue #7544 : Preallocate thread memory before creating the thread to avoid a
...
fatal error in low memory condition.
2010-03-03 23:20:25 +00:00
Florent Xicluna
8af970ab58
Revert a nonexistent docstring typo, r42805.
2010-03-03 11:49:53 +00:00
Gregory P. Smith
9e5d1327f8
Issue #7242 : On Solaris 9 and earlier calling os.fork() from within a
...
thread could raise an incorrect RuntimeError about not holding the import
lock. The import lock is now reinitialized after fork.
2010-03-01 01:22:39 +00:00
Amaury Forgeot d'Arc
adfc80bd81
#4852 : Remove dead code in every thread implementation, unused for many years.
2010-02-23 23:19:39 +00:00
Benjamin Peterson
ee46101e68
remove pointless error checking
2010-02-06 19:40:18 +00:00
Benjamin Peterson
565d78586b
normalize exceptions passed to the __exit__ method #7853
...
In Python 2.x, exceptions in finally blocks are not normalized. Since with
statements are implemented using finally blocks, ceval.c had to be tweaked to
distinguish between with finally blocks and normal ones.
A test for the finalization of generators containing with statements was also
added.
2010-02-05 02:12:14 +00:00
Victor Stinner
b4b0a2935d
Issue #7819 : Check sys.call_tracing() arguments types.
...
py3k was already patched by issue #3661 .
2010-01-31 22:32:15 +00:00
Eric Smith
ee931b7253
Issue #7766 : Change sys.getwindowsversion() return value to a named tuple and add the additional members returned in an OSVERSIONINFOEX structure. The new members are service_pack_major, service_pack_minor, suite_mask, and product_type.
2010-01-27 00:28:29 +00:00
Mark Dickinson
8cd0a66a0f
dtoa.c fix from upstream that fixes incorrectly rounded results for certain subnormals that are also halfway cases.
2010-01-23 21:25:53 +00:00
Mark Dickinson
fc5290458d
Issue #7743 : Add checks for zero inputs to the lshift and mult functions;
...
this fixes the first bug described in issue #7743 .
2010-01-23 20:48:56 +00:00
Mark Dickinson
adcda3400f
Issue #7743 : Fix a potential incorrect rounding bug in dtoa.c (2nd bug
...
in issue 7743).
2010-01-22 17:04:07 +00:00
Mark Dickinson
86db34207c
Correct typo in comment.
2010-01-22 16:18:09 +00:00
Mark Dickinson
ca6ea56718
Additional explanatory comments for _Py_dg_strtod.
2010-01-20 21:23:25 +00:00
Mark Dickinson
1942806013
Don't try to put a value into a NULL pointer.
2010-01-20 18:02:41 +00:00
Mark Dickinson
4141d65fb7
Various dtoa.c cleanups. 1. Despagghetify _Py_dg_strtod parsing code
...
and exit points. 2. Simplify bigcomp comparison loop. 3. Don't set
ERANGE on _Py_dg_strtod underflow (it was set inconsistently anyway).
4. Remove unused dsign field from BCinfo struct.
2010-01-20 17:36:31 +00:00
Mark Dickinson
9481c576cd
Issue #7632 : When Py_USING_MEMORY_DEBUGGER is defined, disable the
...
private memory allocation scheme in dtoa.c, along with a piece of code
that caches powers of 5 for future use. This makes it easier to
detect dtoa.c memory leaks with Valgrind or similar tools.
Patch by Stefan Krah.
2010-01-17 20:57:56 +00:00
Mark Dickinson
23df3d270d
Issue #7632 : Fix a memory leak in _Py_dg_strtod.
2010-01-17 13:37:57 +00:00
Mark Dickinson
18a818bc63
Fix multiple uses of variable 'L' in _Py_dg_strtod, where one use requires an unsigned long and the other a signed long. See also r77421.
2010-01-16 18:06:17 +00:00
Mark Dickinson
811ff822f8
Issue #7632 : Fix one more case of incorrect rounding for str -> float
...
conversion (see bug 5 in the issue tracker).
2010-01-16 17:57:49 +00:00
Mark Dickinson
476279f18b
Issue #7632 : Fix a serious wrong output bug for string -> float conversion.
...
Also remove some now unused variables, and add comments clarifying the
possible outputs of the parsing section of _Py_dg_strtod. Thanks
Eric Smith for reviewing.
2010-01-16 10:44:00 +00:00
Brett Cannon
0bc77474aa
Remove C++/C99-style comments.
2010-01-15 01:31:45 +00:00
Brett Cannon
3ffa43db48
The silencing of DeprecationWarning was not taking -3 into consideration. Since
...
Py3K warnings are DeprecationWarning by default this was causing -3 to
essentially be a no-op. Now DeprecationWarning is only silenced if -3 is not
used.
Closes issue #7700 . Thanks Ezio Melotti and Florent Xicluna for patch help.
2010-01-14 20:00:28 +00:00
Mark Dickinson
f8747c1f12
Issue 7632: fix incorrect rounding for long input strings with values very close to a power of 2. (See Bug 4 in the tracker discussion.)
2010-01-14 14:40:20 +00:00
Mark Dickinson
50b60c612e
Issue 7632: fix a dtoa.c bug (bug 6) causing incorrect rounding. Tests to follow.
2010-01-14 13:14:49 +00:00
Mark Dickinson
03774fac62
Fix off-by-one error introduced in r77483. I have a test for this, but it currently fails due to a different dtoa.c bug; I'll add the test once that bug is fixed.
2010-01-14 13:02:36 +00:00
Mark Dickinson
d2a9940acb
More dtoa.c cleanup; remove the need for bc.dplen, bc.dp0 and bc.dp1.
2010-01-13 22:20:10 +00:00
Mark Dickinson
02139d74ba
Fix buggy comparison: LHS of comparison was being treated as unsigned.
2010-01-13 22:15:53 +00:00
Mark Dickinson
6e0d3d67fb
Simplify and annotate the bigcomp function, removing unused special cases.
2010-01-13 20:55:03 +00:00
Mark Dickinson
5818e01253
Clarify that sulp expects a nonnegative input, but that +0.0 is fine.
2010-01-13 19:02:37 +00:00
Mark Dickinson
b26d56ac18
Add comments explaining the role of the bigcomp function in dtoa.c.
2010-01-13 18:21:53 +00:00
Mark Dickinson
5ff4f279e6
Issue #7632 : Fix a bug in dtoa.c that could lead to incorrectly-rounded results.
2010-01-12 22:55:51 +00:00
Mark Dickinson
8efef5ce9f
Issue #7632 : Fix a problem with _Py_dg_strtod that could lead to
...
crashes in debug builds, for certain long numeric strings
corresponding to subnormal values.
2010-01-12 22:23:56 +00:00
Alexandre Vassalotti
102d70e06c
Update version information for AST changes in r77422.
2010-01-11 22:46:43 +00:00
Alexandre Vassalotti
b646547bb4
Issue #2333 : Backport set and dict comprehensions syntax.
2010-01-11 22:36:12 +00:00
Mark Dickinson
0ca7452794
Change a variable type to avoid signed overflow; replace repeated '19999' constant by a define.
2010-01-11 17:15:13 +00:00
Mark Dickinson
5a0b399aa9
Remove unused BCinfo fields and an unused macro.
2010-01-10 13:06:31 +00:00
Brett Cannon
6fdd3dcb6a
DeprecationWarning is now silent by default.
...
This was originally suggested by Guido, discussed on the stdlib-sig mailing
list, and given the OK by Guido directly to me. What this change essentially
means is that Python has taken a policy of silencing warnings that are only
of interest to developers by default. This should prevent users from seeing
warnings which are triggered by an application being run against a new
interpreter before the app developer has a chance to update their code.
Closes issue #7319 . Thanks to Antoine Pitrou, Ezio Melotti, and Brian Curtin
for helping with the issue.
2010-01-10 02:56:19 +00:00