- 01 Şub, 2001 1 kayıt (commit)
-
-
Jeremy Hylton yazdı
PyFPE_END_PROTECT() was called on undefined var
-
- 17 Ock, 2001 1 kayıt (commit)
-
-
Guido van Rossum yazdı
- Get rid of float_cmp(). - Renamed Py_TPFLAGS_NEWSTYLENUMBER to Py_TPFLAGS_CHECKTYPES.
-
- 08 Ock, 2001 1 kayıt (commit)
-
-
Neil Schemenauer yazdı
-
- 04 Ock, 2001 1 kayıt (commit)
-
-
Neil Schemenauer yazdı
-
- 24 Eki, 2000 1 kayıt (commit)
-
-
Fred Drake yazdı
Changes to error messages to increase consistency & clarity. This (mostly) closes SourceForge patch #101839.
-
- 06 Eki, 2000 1 kayıt (commit)
-
-
Tim Peters yazdı
raise ValueError. Checked in the patch as far as it went, but also changed all of ints, longs and floats to raise ZeroDivisionError instead when raising 0 to a negative number. This is what 754-inspired stds require, as the "true result" is an infinity obtained from finite operands, i.e. it's a singularity. Also changed float pow to not be so timid about using its square-and-multiply algorithm. Note that what math.pow does is unrelated to what builtin pow does, and will still vary by platform.
-
- 26 Eyl, 2000 1 kayıt (commit)
-
-
Fred Drake yazdı
Add definitions of INT_MAX and LONG_MAX to pyport.h. Remove includes of limits.h and conditional definitions of INT_MAX and LONG_MAX elsewhere. This closes SourceForge patch #101659 and bug #115323.
-
- 25 Eyl, 2000 1 kayıt (commit)
-
-
Tim Peters yazdı
fncs are allowed to raise SIGFPE (see the C std), but OK by me if people using --with-fpectl want to pay for checking anyway.
-
- 23 Eyl, 2000 1 kayıt (commit)
-
-
Tim Peters yazdı
I fixed the specific complaint but left the (many) large issues untouched. See the (very long) bug report discussion for why: http://sourceforge.net/bugs/?func=detailbug&group_id=5470&bug_id=110624 Note that while I left the interface to the undocumented public API function PyFloat_FromString alone, its 2nd argument is useless. From a comment block in the code: RED_FLAG 22-Sep-2000 tim PyFloat_FromString's pend argument is braindead. Prior to this RED_FLAG, 1. If v was a regular string, *pend was set to point to its terminating null byte. That's useless (the caller can find that without any help from this function!). 2. If v was a Unicode string, or an object convertible to a character buffer, *pend was set to point into stack trash (the auto temp vector holding the character buffer). That was downright dangerous. Since we can't change the interface of a public API function, pend is still supported but now *officially* useless: if pend is not NULL, *pend is set to NULL.
-
- 16 Eyl, 2000 1 kayıt (commit)
-
-
Tim Peters yazdı
FRED, please check my monkey-see-monkey-do Tex fiddling!
-
- 01 Eyl, 2000 1 kayıt (commit)
-
-
Guido van Rossum yazdı
This should match the situation in the 1.6b1 tree.
-
- 18 Agu, 2000 1 kayıt (commit)
-
-
Barry Warsaw yazdı
scope. Previously, s_buffer[] was defined inside the PyUnicode_Check() scope, but referred to in the outer scope via assignment to s. This quiets an Insure portability warning.
-
- 15 Agu, 2000 1 kayıt (commit)
-
-
http://sourceforge.net/bugs/?func=detailbug&bug_id=111866&group_id=5470Tim Peters yazdı
This was a misleading bug -- the true "bug" was that hash(x) gave an error return when x is an infinity. Fixed that. Added new Py_IS_INFINITY macro to pyport.h. Rearranged code to reduce growing duplication in hashing of float and complex numbers, pushing Trent's earlier stab at that to a logical conclusion. Fixed exceedingly rare bug where hashing of floats could return -1 even if there wasn't an error (didn't waste time trying to construct a test case, it was simply obvious from the code that it *could* happen). Improved complex hash so that hash(complex(x, y)) doesn't systematically equal hash(complex(y, x)) anymore.
-
- 12 Agu, 2000 1 kayıt (commit)
-
-
Trent Mick yazdı
return value to int is safe here because it previously checked that there will be no overflow.
-
- 31 Tem, 2000 1 kayıt (commit)
-
-
Peter Schneider-Kamp yazdı
marked my*.h as obsolete
-
- 09 Tem, 2000 3 kayıt (commit)
-
-
Fred Drake yazdı
the standard for Python implementation.
-
Fred Drake yazdı
-
Tim Peters yazdı
-
- 30 Haz, 2000 3 kayıt (commit)
-
-
Guido van Rossum yazdı
-
Guido van Rossum yazdı
-
Fred Drake yazdı
The common technique for printing out a pointer has been to cast to a long and use the "%lx" printf modifier. This is incorrect on Win64 where casting to a long truncates the pointer. The "%p" formatter should be used instead. The problem as stated by Tim: > Unfortunately, the C committee refused to define what %p conversion "looks > like" -- they explicitly allowed it to be implementation-defined. Older > versions of Microsoft C even stuck a colon in the middle of the address (in > the days of segment+offset addressing)! The result is that the hex value of a pointer will maybe/maybe not have a 0x prepended to it. Notes on the patch: There are two main classes of changes: - in the various repr() functions that print out pointers - debugging printf's in the various thread_*.h files (these are why the patch is large) Closes SourceForge patch #100505.
-
- 29 Haz, 2000 1 kayıt (commit)
-
-
Fred Drake yazdı
errors in some of the hash algorithms. For exmaple, in float_hash and complex_hash a certain part of the value is not included in the hash calculation. See Tim's, Guido's, and my discussion of this on python-dev in May under the title "fix float_hash and complex_hash for 64-bit *nix" (2) The hash algorithms that use pointers (e.g. func_hash, code_hash) are universally not correct on Win64 (they assume that sizeof(long) == sizeof(void*)) As well, this patch significantly cleans up the hash code. It adds the two function _Py_HashDouble and _PyHash_VoidPtr that the various hashing routine are changed to use. These help maintain the hash function invariant: (a==b) => (hash(a)==hash(b))) I have added Lib/test/test_hash.py and Lib/test/output/test_hash to test this for some cases.
-
- 03 May, 2000 1 kayıt (commit)
-
-
Guido van Rossum yazdı
For more comments, read the patches@python.org archives. For documentation read the comments in mymalloc.h and objimpl.h. (This is not exactly what Vladimir posted to the patches list; I've made a few changes, and Vladimir sent me a fix in private email for a problem that only occurs in debug mode. I'm also holding back on his change to main.c, which seems unnecessary to me.)
-
- 05 Nis, 2000 1 kayıt (commit)
-
-
Guido van Rossum yazdı
his copy of test_contains.py seems to be broken -- the lines he deleted were already absent). Checkin messages: New Unicode support for int(), float(), complex() and long(). - new APIs PyInt_FromUnicode() and PyLong_FromUnicode() - added support for Unicode to PyFloat_FromString() - new encoding API PyUnicode_EncodeDecimal() which converts Unicode to a decimal char* string (used in the above new APIs) - shortcuts for calls like int(<int object>) and float(<float obj>) - tests for all of the above Unicode compares and contains checks: - comparing Unicode and non-string types now works; TypeErrors are masked, all other errors such as ValueError during Unicode coercion are passed through (note that PyUnicode_Compare does not implement the masking -- PyObject_Compare does this) - contains now works for non-string types too; TypeErrors are masked and 0 returned; all other errors are passed through Better testing support for the standard codecs. Misc minor enhancements, such as an alias dbcs for the mbcs codec. Changes: - PyLong_FromString() now applies the same error checks as does PyInt_FromString(): trailing garbage is reported as error and not longer silently ignored. The only characters which may be trailing the digits are 'L' and 'l' -- these are still silently ignored. - string.ato?() now directly interface to int(), long() and float(). The error strings are now a little different, but the type still remains the same. These functions are now ready to get declared obsolete ;-) - PyNumber_Int() now also does a check for embedded NULL chars in the input string; PyNumber_Long() already did this (and still does) Followed by: Looks like I've gone a step too far there... (and test_contains.py seem to have a bug too). I've changed back to reporting all errors in PyUnicode_Contains() and added a few more test cases to test_contains.py (plus corrected the join() NameError).
-
- 10 Mar, 2000 1 kayıt (commit)
-
-
Guido van Rossum yazdı
-
- 20 Ock, 2000 1 kayıt (commit)
-
-
Guido van Rossum yazdı
compilation on NT Alpha. Mostly added casts etc.
-
- 23 Ara, 1999 1 kayıt (commit)
-
-
Guido van Rossum yazdı
while str() uses %.12g as before.
-
- 12 Eki, 1999 1 kayıt (commit)
-
-
Barry Warsaw yazdı
messages for specific changes.
-
- 06 May, 1999 1 kayıt (commit)
-
-
Guido van Rossum yazdı
1. Fixes float divmod so that the quotient it returns is always an integral value. 2. Fixes float % and float divmod so that the remainder always gets the right sign (the current code uses a "are the signs different?" test that doesn't work half the time <wink> when the product of the divisor and the remainder underflows to 0).
-
- 19 Mar, 1999 1 kayıt (commit)
-
-
Guido van Rossum yazdı
a block cannot be freed, add its free items back to the free list. This is necessary to avoid leaking when Python is reinitialized later.
-
- 12 Mar, 1999 2 kayıt (commit)
-
-
Guido van Rossum yazdı
represented by an explicit structure. (There are still too many casts in the code, but that may be unavoidable.) Also added code so that with -vv it is very chatty about what it does.
-
Guido van Rossum yazdı
so here's his patch again. This time it works (at least on Solaris, Linux and Irix).
-
- 11 Mar, 1999 1 kayıt (commit)
-
-
Guido van Rossum yazdı
alignment?), and I didn't test it. Withdrawing it for now.
-
- 10 Mar, 1999 1 kayıt (commit)
-
-
Guido van Rossum yazdı
floats on finalization.
-
- 31 Eki, 1997 1 kayıt (commit)
-
-
Guido van Rossum yazdı
in libmath.a so they are available to mathmodule.so (in case it is shared). While this still gets triggered on Solaris 2.x, this appears to be harmless there.
-
- 05 Agu, 1997 1 kayıt (commit)
-
-
Guido van Rossum yazdı
-
- 13 May, 1997 1 kayıt (commit)
-
-
Guido van Rossum yazdı
By Aaron Watters.
-
- 02 May, 1997 1 kayıt (commit)
-
-
Guido van Rossum yazdı
-
- 14 Mar, 1997 1 kayıt (commit)
-
-
Guido van Rossum yazdı
-
- 14 Şub, 1997 1 kayıt (commit)
-
-
Guido van Rossum yazdı
Surround various f.p. operations with PyFPE_{START,END}_PROTECT macros.
-