3 ms·
Sure, it wasn't so much a conclusion as a reaction to: python 3.0 asynchronous i/o. First because python 3 is far less exciting than its version number could i
by 0xdeadbeefbabe 13y ago
Sure, it wasn't so much a conclusion as a reaction to: python 3.0 asynchronous i/o. First because python 3 is far less exciting than its version number could imply, and because async i/o is something twisted python could do well for at least a decade, a long time before node.js, tornado, and others ohh almost forgot and tulip with python 3.0.
Edit: remember tulip.