cpython.git - https://github.com/python/cpython.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Issue #8748: Fix incorrect results from comparisons between an integer	Mark Dickinson	2010-05-30	1	-1/+18
\| \| \| \|	and a complex instance. Based on a patch by Meador Inge.
*	Issue #5211: Complete removal of implicit coercions for the complex	Mark Dickinson	2010-05-30	1	-0/+13
\| \| \| \| \|	type. Coercion for arithmetic operations was already removed in r78280, but that commit didn't remove coercion for rich comparisons.
*	Replace catch_warnings with check_warnings when it makes sense. Use ↵	Florent Xicluna	2010-03-31	1	-13/+5
\| \| \| \|	assertRaises context manager to simplify some tests.
*	Issue #7988: Fix default alignment to be right aligned for ↵	Eric Smith	2010-02-22	1	-0/+2
\| \| \| \|	complex.__format__. Now it matches other numeric types.
*	Issue #5211: Fix complex type to avoid implicit calls to	Mark Dickinson	2010-02-21	1	-0/+55
\| \| \| \|	complex.__coerce__. Thanks Meador Inge for the patch.
*	Remove e assertIs definitions and use correct assert* methods.	Ezio Melotti	2010-02-20	1	-3/+0
\|
*	Issue #3382: Make '%F' and float.__format__('F') convert results to upper ↵	Eric Smith	2009-11-29	1	-0/+19
\| \| \| \|	case. Much of the patch came from Mark Dickinson.
*	Issue #7117: Use PyOS_string_to_double instead of PyOS_ascii_strtod in	Mark Dickinson	2009-10-26	1	-1/+4
\| \| \| \| \|	complexobject.c. Also remove length restriction on unicode inputs to the complex constructor.
*	convert usage of fail* to assert*	Benjamin Peterson	2009-06-30	1	-5/+5
\|
*	Issue #5829: don't raise OverflowError for complex('1e500'). Backport of ↵	Mark Dickinson	2009-05-20	1	-0/+7
\| \| \| \|	r72803.
*	Issue #5920: Changed format.__float__ and complex.__float__ to use a ↵	Eric Smith	2009-05-05	1	-0/+10
\| \| \| \|	precision of 12 when using the empty presentation type. This more closely matches str()'s behavior and reduces surprises when adding alignment flags to an empty format string. Patch by Mark Dickinson.
*	Issue #1588: Add complex.__format__.	Eric Smith	2009-04-30	1	-1/+60
\|
*	Fix typo in complex parsing code; expand tests.	Mark Dickinson	2009-04-25	1	-3/+19
\|
*	Issue #5816:	Mark Dickinson	2009-04-24	1	-10/+66
\| \| \| \| \| \| \| \|	- simplify parsing and printing of complex numbers - make complex(repr(z)) round-tripping work for complex numbers involving nans, infs, or negative zeros - don't accept some of the stranger complex strings that were previously allowed---e.g., complex('1..1j')
*	Fixed complex.__getnewargs__() to not emit another complex object.	Alexandre Vassalotti	2008-06-04	1	-0/+8
\|
*	Fixed repr() and str() of complex numbers. Complex suffered from the same ↵	Christian Heimes	2008-02-15	1	-0/+14
\| \| \| \|	problem as floats but I forgot to test and fix them.
*	Issue #1678380. Fix a bug that identifies 0j and -0j when they appear	Mark Dickinson	2008-01-31	1	-0/+7
\| \| \| \| \|	in the same code unit. The fix is essentially the same as the fix for a previous bug identifying 0. and -0.
*	Patch # 1507 by Mark Dickinson. Make complex(x, -0) retain the sign of	Guido van Rossum	2007-11-27	1	-0/+13
\| \| \| \| \|	the imaginary part (as long as it's not complex). Backport candidate?
*	Patch #1491866: change the complex() constructor to allow parthensized ↵	Collin Winter	2007-03-09	1	-0/+12
\| \| \| \|	forms. This means complex(repr(x)) now works instead of raising a ValueError.
*	Test case for latest complexobject fix.	Georg Brandl	2005-09-17	1	-0/+2
\|
*	Make subclasses of int, long, complex, float, and unicode perform type	Brett Cannon	2005-04-26	1	-0/+22
\| \| \| \| \| \| \|	conversion using the proper magic slot (e.g., __int__()). Also move conversion code out of PyNumber_() functions in the C API into the nb_ function. Applied patch #1109424. Thanks Walter Doewald.
*	Fix repr for negative imaginary part. Fixes #1013908.	Martin v. Löwis	2004-08-22	1	-0/+1
\|
*	Remove useless import.	Walter Dörwald	2003-08-05	1	-1/+1
\|
*	Check both __div__ and __truediv__ in division tests.	Walter Dörwald	2003-08-05	1	-1/+9
\| \| \| \|	(From SF patch #543867)
*	Add various test cases from SF patch 543867.	Walter Dörwald	2003-07-15	1	-1/+58
\|
*	Whitespace normalization.	Tim Peters	2003-06-29	1	-1/+1
\|
*	Port test_complex.py to unittest.	Walter Dörwald	2003-06-18	1	-89/+249
\| \| \| \| \| \| \| \|	Move the constructor tests from test_builtin to test_complex. Add a bunch of tests (code coverage is a 94%). From SF patch #736962.
*	Complete the absolute import patch for the test suite. All relative	Barry Warsaw	2002-07-30	1	-1/+1
\| \| \| \| \| \| \| \|	imports of test modules now import from the test package. Other related oddities are also fixed (like DeprecationWarning filters that weren't specifying the full import part, etc.). Also did a general code cleanup to remove all "from test.test_support import "'s. Other from...import 's weren't changed.
*	test_support: add a docstring to vereq().	Tim Peters	2001-12-29	1	-2/+1
\| \| \| \|	test_complex: repair new test's usage of vereq().
*	SF Patch #497487 add test to compare conjugate of a complex number	Neal Norwitz	2001-12-29	1	-1/+4
\|
*	SF Patch #494873 add tests for complex numbers including calls to int()/long()	Neal Norwitz	2001-12-29	1	-0/+21
\|
*	Add a comment explaining what these tests are for, and where to look for	Fred Drake	2001-12-13	1	-0/+3
\| \| \| \|	tests of complex().
*	Reverting to rev 1.2. Apparently gcc doesn't use the extended-precision	Tim Peters	2001-09-06	1	-3/+16
\| \| \| \| \| \| \| \|	capabilities of the Pentium FPU, so what should have been (and were on Windows) exact results got fuzzy. Then it turns out test_support.fcmp() isn't tolerant of tiny errors when one of the comparands is 0, but test_complex's old check_close_real() is. Rather than fix gcc <wink>, easier to revert this test and revisit after the release.
*	Rewrite to use test_support's fine fcmp instead -- I didn't know that	Tim Peters	2001-09-06	1	-16/+3
\| \| \| \|	existed when I wrote this test.
*	This division test was too stringent in its accuracy expectations for	Tim Peters	2001-05-29	1	-4/+4
\| \| \| \| \| \| \|	random inputs: if you ran the test 100 times, you could expect it to report a bogus failure. So loosened its expectations. Also changed the way failing tests are printed, so that when run under regrtest.py we get enough info to reproduce the failure.
*	SF bug [ #409448 ] Complex division is braindead	Tim Peters	2001-03-18	1	-0/+65
	http://sourceforge.net/tracker/?func=detail&aid=409448&group_id=5470&atid=105470 Now less braindead. Also added test_complex.py, which doesn't test much, but fails without this patch.