http://bugzilla.suse.com/show_bug.cgi?id=997614 http://bugzilla.suse.com/show_bug.cgi?id=997614#c11 --- Comment #11 from Robert Schweikert <rjschwei@suse.com> --- I understand that this is not very nice work. However, deprecated != should not work a deprecated function should still work as expected until it is removed, which happens in Python 3.7, not in Python 3.6. Additionally, on TW: -> python Python 2.7.14 (default, Oct 12 2017, 15:50:02) [GCC] on linux2 Type "help", "copyright", "credits" or "license" for more information.
import platform platform.dist() ('', '', '')
Here the argument of "it's deprecated" is not valid at all as the function is marked deprecated in 3.5+ . I understand that Python 2 is supposed to disappear from TW, but in SLE 15 the Legacy Module with contain Python 2 which will have support for 2 years after release and I expect the behavior of Python 2 in SLE 15 to mimic that of TW, i.e. the function is broken. On TW: -> python3 Python 3.6.4 (default, Jan 03 2018, 13:52:55) [GCC] on linux Type "help", "copyright", "credits" or "license" for more information.
import platform platform.dist() ('', '', '')
".... Features are deprecated rather than immediately removed, to provide backward compatibility, and to give programmers time to bring affected code into compliance with the new standard." from [1]. How we are providing a transition period when we are simply breaking the feature? [1] https://en.wikipedia.org/wiki/Deprecation -- You are receiving this mail because: You are on the CC list for the bug.