[issue29625] colorsys.rgb_to_hsv always returns saturation as 0 (python2.7 only)

Mark Dickinson added the comment: No problem. I did spend some time wondering whether `rgb_to_hsv` still gives the correct results if any of the inputs happens to be an integer (though still in the range [0, 1]). It looks as though it does, though. --

[issue29625] colorsys.rgb_to_hsv always returns saturation as 0 (python2.7 only)

Will Pittman added the comment: oh, thank you very much and sorry for my negligence! -- stage: -> resolved status: open -> closed ___ Python tracker ___

[issue29625] colorsys.rgb_to_hsv always returns saturation as 0 (python2.7 only)

Mark Dickinson added the comment: The arguments to rgb_to_hsv are supposed to be floating-point numbers in the range 0.0 to 1.0. That's documented here: https://docs.python.org/2/library/colorsys.html > Coordinates in all of these color spaces are floating point values. In the > YIQ space,

[issue29625] colorsys.rgb_to_hsv always returns saturation as 0 (python2.7 only)

Changes by Will Pittman : -- title: colorsys.rgb_to_hsv always returns saturation as 0 (python2.7.13 only) -> colorsys.rgb_to_hsv always returns saturation as 0 (python2.7 only) ___ Python tracker