Stephan Kulow wrote:
Am 01.07.2017 um 15:59 schrieb Michael Ströder:
How do you know that Python code with shee-bang /usr/bin/python is compatible to Python 2.x and 3.x?
If it's not fully compatible how do you avoid damage to your system, security issues etc.?
As you seem to know python 2 vs 3 glitches: do you have any examples of python2 code that worries you to create security issues or damage if run under python3?
Personally I ran into problems where behaviour of custom dict classes is different but does not necessarily lead to exceptions being raised. Just the (caching key lookup) behaviour was different.
My own experiences are rather quite fatal when even trying to run old python code under python3.
You mean you always saw the code clearly failing with exceptions?
In this discussion I heared so far that a python switch would kill users, damage systems and cause security issues. This is tough language for an update about a programming language who's biggest harm is the abuse of whitespace ;)
The main problem with this discussion is that pretty simple assumptions are made even ignoring PEP advice without thorough analysis of all the affected Python code shipped with openSUSE (which is impossible). Ciao, Michael.