Updates:
Status: Verified
Comment #7 on issue 1799 by brownian.box: output-distance.py does not parse
scheme nan values correctly
http://code.google.com/p/lilypond/issues/detail?id=1799
(No comment was entered for this change.)
___
Comment #4 on issue 1799 by mts...@gmail.com: output-distance.py does not
parse scheme nan values correctly
http://code.google.com/p/lilypond/issues/detail?id=1799
Fix pushed as 7cd9444ea5dfc80782befa6b64bae015bddbd967.
___
bug-lilypond mailing
Updates:
Status: Fixed
Labels: fixed_2_15_8
Comment #5 on issue 1799 by percival.music.ca: output-distance.py does not
parse scheme nan values correctly
http://code.google.com/p/lilypond/issues/detail?id=1799
(No comment was entered for this change.)
Updates:
Labels: -Patch-review -fixed_2_15_8 fixed_2_15_9
Comment #6 on issue 1799 by n.putt...@gmail.com: output-distance.py does
not parse scheme nan values correctly
http://code.google.com/p/lilypond/issues/detail?id=1799
(No comment was entered for this change.)
Updates:
Labels: -Patch-new Patch-review
Comment #2 on issue 1799 by colinpkc...@gmail.com: output-distance.py does
not parse scheme nan values correctly
http://code.google.com/p/lilypond/issues/detail?id=1799
Passes make and reg tests.
Status: Accepted
Owner:
Labels: Type-Build Priority-High Patch-new
New issue 1799 by mts...@gmail.com: output-distance.py does not parse
scheme nan values correctly
http://code.google.com/p/lilypond/issues/detail?id=1799
nan values in scheme are issued as +nan.0 and -nan.0, which Python
Comment #1 on issue 1799 by mts...@gmail.com: output-distance.py does not
parse scheme nan values correctly
http://code.google.com/p/lilypond/issues/detail?id=1799
It seems that my patch fixes the problem - I applied it to the branch where
I'm running my stem regtests, and now the regtests
