Numbers with small errors introduced by their floating point representation are output correctly. ex 12.870000000000001 -> 12.87, 64.13999999999999 -> 64.14
Whole numbers which were emitted with a trailing 0 now have no trailing 0. ex: 2.0 -> 2. This required some changes in the existing test cases. The output now more closely matches the way numbers are represented in the SVG spec examples. It's easiest to see this in the changes to test.test_generation.TestGeneration.test_path_parsing.
Some small floating point numbers now emit fewer significant digits. ex: 206.07112 -> 206.071 in test.test_groups.TestGroups.test_add_group. This is chosen by python's idea of which representation is the 'best' as explained here
This change also removes the need for special python2/3 casing in test.test_generation.TestGeneration.test_path_parsing since the behavior of g is the same in both. It may be possible to further simplify this test.
Format the floating point numbers output by
Path.dto avoid a bunch of .x0000000000001 and .x999999999999 noise. Fixes https://github.com/mathandy/svgpathtools/issues/223.Changed behavior:
Numbers with small errors introduced by their floating point representation are output correctly. ex
12.870000000000001->12.87,64.13999999999999->64.14Whole numbers which were emitted with a trailing 0 now have no trailing 0. ex:
2.0->2. This required some changes in the existing test cases. The output now more closely matches the way numbers are represented in the SVG spec examples. It's easiest to see this in the changes totest.test_generation.TestGeneration.test_path_parsing.Some small floating point numbers now emit fewer significant digits. ex:
206.07112->206.071intest.test_groups.TestGroups.test_add_group. This is chosen by python's idea of which representation is the 'best' as explained hereThis change also removes the need for special python2/3 casing in
test.test_generation.TestGeneration.test_path_parsingsince the behavior ofgis the same in both. It may be possible to further simplify this test.