Message 334379 - Python tracker

Message334379

Author	FR4NKESTI3N
Recipients	FR4NKESTI3N, Petter S, lisroach, xtreak
Date	2019-01-25.23:30:19
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1548459019.37.0.0223445753492.issue35656@roundup.psfhosted.org>
In-reply-to

Content
> due to floating-point inexactness +1 Its not easy to predict when calculated value will not be equal to expected theoretical value. for example math.cos(radians(90)) is something like 6e-17 rather than 0. Testing for this exact value would be just awkward. assertAlmostEqual() is already there in unittest for such comparisons so it wouldn't be completely nonsensical to have something like APPROX

Content

> due to floating-point inexactness
+1 Its not easy to predict when calculated value will not be equal to expected theoretical value. for example math.cos(radians(90)) is something like 6e-17 rather than 0.
Testing for this exact value would be just awkward.
assertAlmostEqual() is already there in unittest for such comparisons so it wouldn't be completely nonsensical to have something like APPROX

History
Date	User	Action	Args
2019-01-25 23:30:21	FR4NKESTI3N	set	recipients: + FR4NKESTI3N, lisroach, Petter S, xtreak
2019-01-25 23:30:19	FR4NKESTI3N	set	messageid: <1548459019.37.0.0223445753492.issue35656@roundup.psfhosted.org>
2019-01-25 23:30:19	FR4NKESTI3N	link	issue35656 messages
2019-01-25 23:30:19	FR4NKESTI3N	create