4 ms·
No, it's legacy behavior and the community took the opportunity to fix it in Python 3, where it raises a SyntaxError. Python 2 has _many_ quirks like this one.
by sametmax 8y ago
No, it's legacy behavior and the community took the opportunity to fix it in Python 3, where it raises a SyntaxError.
Python 2 has _many_ quirks like this one. Python 3 was not just "it's unicode".