I didn't touch Python3 until PyCon, and my first user experience is not really good. I've got a feeling that Python3 became more ugly, because it doesn't allow me to think about the logic anymore, and requires more low-level workarounds even for basic user input/output. For example, now I need to remember that on Windows I need to flush output every time when I want the result of print() with end!='\n' to appear on the screen immediately. And for the most of my legacy scripts I used end='\n' when I want to output some progress to user. I am surprised to know this never worked on Linux, but what I really didn't expect is to see that choice is made not in user's favor, but in a favor of speed. This way we'll be writing in a cross-platform assembly language named 'Python' soon. =) http://bugs.python.org/issue11633 -- anatoly t.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4