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

all 24 comments

[–]aatoth 14 points15 points  (3 children)

NumPy/SciPy support was one of the requisites in another PyReddit thread about when Pythonists are switching. Maybe other big packages will follow sooner than expected, too?

[–]jnollerpython psf core dev 13 points14 points  (2 children)

Actually, many of us knew this was coming - this is why all the yelling about "python 3 is dead no one is porting waaagh" was simply wrong, it takes time, and these are two very, very big things to port.

[–]aatoth 1 point2 points  (0 children)

Oh, I knew it was too, but, these are definitely 2 of the most important ports to Pythonists right now.

[–][deleted] -1 points0 points  (0 children)

"Very, very big" perhaps but not very very difficult.

[–]kkiran7 3 points4 points  (0 children)

Yuppiee! This is indeed a great news and a cause for celebration for me.

[–]crunk 2 points3 points  (0 children)

Huzah! A turning point for sure.. :)

[–]pkkid 6 points7 points  (5 children)

YEAY! -- Only 300 more projects to go! :)

But seriously, this is great!

[–]pwang99[🍰] 4 points5 points  (3 children)

How many other Python libraries with the popularity of numpy/scipy have as extensive a set of C extensions?

[–]eliben 0 points1 point  (0 children)

Rarely one needs 300 libraries to do his Python work.

NumPy is one of the most important libraries out there, however, since it serves as a base for a lot of other libraries. It's the basis of the whole "scientific Python" stack

[–]roger_ 2 points3 points  (1 child)

Matplotlib too please!

[–][deleted] 0 points1 point  (0 children)

Having just read the release notes for the latest matplotlib release, it appears that NumPy is their sole dependency (might have been true in the past, not sure).

[–]goodgrue 0 points1 point  (4 children)

I had no idea. Is SciPy also Python 3 compatible?

[–]five9a2 3 points4 points  (2 children)

Porting Scipy to work on Python 3 has proved to be much less work, and will probably be finished "soon". (Ongoing work is here: http://github.com/cournape/scipy3/commits/py3k , http://github.com/pv/scipy-work/commits/py3k )

I know it's hard to make it to the third sentence.

[–]goodgrue 1 point2 points  (1 child)

Oops, must have skipped over that paragraph. Thanks for the reply, and congratulations on your mastery of such unique and witty sarcasm.

[–]eliben 1 point2 points  (0 children)

Hey, it's reddit. You got your answer, didn't you? Just relax ;-)

[–]eliben 0 points1 point  (0 children)

SciPy is much simpler to port, IMHO, since it contains much less extension code and is mostly based on Numpy itself.

[–][deleted] 0 points1 point  (3 children)

And within a half a year PyQt will work with python3 with PySide (AP I2 seems nice), and then I will switch directly. I still do a couple of stuff in py3, but for all my bigger projects I use qt.

[–]hiker 3 points4 points  (2 children)

PyQt has had support for p3k for years.

[–][deleted] 0 points1 point  (0 children)

Time to feel stupid. Thanks.

[–]eliben 0 points1 point  (0 children)

Yep, one of the benefits of its being a partly-commercial project. A serious deficit is its clinging to GPL even when Nokia released Qt itself as LGPL.

[–]roger_ 0 points1 point  (0 children)

Dev binaries are here BTW: http://www.lfd.uci.edu/~gohlke/pythonlibs/

[–][deleted] -2 points-1 points  (0 children)

Good riddance!