3 ms·
I've been doing a ton of Python work lately. Frankly, in my experience, Python 3 is more of a pain to develop with, primarily due to two factors: * Encoding sp
by pnathan 16y ago
I've been doing a ton of Python work lately. Frankly, in my experience, Python 3 is more of a pain to develop with, primarily due to two factors:
* Encoding specifications required.
* maps/reduces returning iterators objects instead of a list. Having to call list() on anything I map is just a pain.
I don't plan to switch to Python 3 until a compelling reason shows up. 2.7 works great for what I do.
The real story here is how Python 3 appears to be a largely unwanted improvement, IMO.
- briancurtin 16y agomaps/reduces returning iterators objects instead of a list. Having to call list() on anything I map is just a pain. Why do you require it to be a list?
- metageek 16y agoI like that map and reduce return iterators; it lets me map over a huge collection even if I just want the first few.
- leon_ 16y agoTo me py3 has far too few "killer features" to switch. I just keep using 2.6 for my stuff because a) it does the job and b) it's just a major inconvenience without any benefits to port everything to 3.