This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients Evelyn Mitchell, mark.dickinson, ned.deily
Date 2016-08-15.11:02:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471258949.83.0.0898787437476.issue27763@psf.upfronthosting.co.za>
In-reply-to
Content
> in looking through test_cmath, it appears that only the two numeric
> argument form of complex(i, j) is tested for any of the functions, not the
> complex('i+nj') string form.

We're testing the cmath functions on complex number inputs; I don't think it matters much how those complex numbers are created. The string form of the constructor can't create any complex numbers that the two-argument `complex(x, y)` form can't, so we're not losing test coverage by only using the `complex(x, y)` form.

The complex number creation from both strings and pairs of floats should be tested independently, of course.
History
Date User Action Args
2016-08-15 11:02:29mark.dickinsonsetrecipients: + mark.dickinson, ned.deily, Evelyn Mitchell
2016-08-15 11:02:29mark.dickinsonsetmessageid: <1471258949.83.0.0898787437476.issue27763@psf.upfronthosting.co.za>
2016-08-15 11:02:29mark.dickinsonlinkissue27763 messages
2016-08-15 11:02:29mark.dickinsoncreate