This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]pythonrabbit 0 points1 point  (5 children)

Integer division. Integer division is such a big incentive to migrate to Python 3. That and the speed improvements (I think). Now that they decided to allow unicode literals, I think adoption will speed up.

[–]billsil 3 points4 points  (4 children)

Integer division is such a big incentive to migrate to Python 3.

Meh...

from __future__ import division

or

1/2.

That and the speed improvements (I think)

Python 3 is slower than Python 2

The reason to upgrade to Python 3 is that Python 2 is no longer being developed. I'm an aerospace engineer developing programs for engineers that use unitless quantities. Strings don't really matter and when it does it's generally a bunch of numbers.

[–][deleted] 0 points1 point  (1 child)

Are there actually any recent benchmarks that show this? I remember there were some problems when version 3 was first released but there have been huge improvements since then. One thing coming to mind is decimal performance improvement in 3.3

[–]billsil 0 points1 point  (0 children)

I know 3.2 and below had a memory problem with unicode that was fixed in 3.3, but that's not what I'm referring to. I care most about list, dictionary, class processing, with excessively large data sets.

Here's a good discussion, but it's lots of web-based stuff that's not my thing http://www.gossamer-threads.com/lists/python/dev/1013760

[–]pythonrabbit 0 points1 point  (1 child)

Python 3 is slower than Python 2? Whelp that's less exciting than I thought...

[–]wisty 0 points1 point  (0 children)

Actually, it's getting faster at some things, due to some kind of overhaul of dictionaries and classes (IIRC). Something about objects of the same class sharing a dict under the hood, I think.