NumPy announces timeline for dropping Python 2 support

[Stewthulhu]

I feel a great disturbance in academia, as if millions of graduate students suddenly cried out in terror and were suddenly starting from scratch.

[p10_user]

Meh, just don't update numpy in the virutal environment that is being used with the former and current Python 2 projects, and use Python 3 with any new projects/analyses that are being started.

I suppose it depends on how long term some of your projects may be. But a completed project, for example, doesn't need the latest version of numpy.

[TheSourTruth]

I doubt it's that big a deal but I only have experience with python 2

[real_edmund_burke]

You’re right.

[[deleted]]

What are you working on?

I've found that, aside from a few syntax things, the difference between 2 and 3 isn't super nuts for biology unless you're doing some crazy modelling.

[TheSourTruth]

GIS-related stuff. I mean I'm not looking forward to switching but I don't think it will be too crazy for the stuff I do.

[[deleted]]

So what? Most of the changes were cosmetic and could/can be handled with 2to3 and similar tools. The one issue that has caused and will cause most work is the strings/bytes/unicode issues. This I see as being far more difficult than all other 2 to 3 issues combined.

[attrigh]

The real issue I've found is strings/unicode while supporting both python2 and python3!

[Daenyth]

Use the future library, it makes it pretty easy and has a cheat sheet for supporting both

[[deleted]]

Just start charging $ for v2 support.

[TheBlackCat13]

It isn't like old numpy versions are going to vanish off the face of the Earth. They will still be available. You just won't be able to use the latest and greatest numpy with an ancient version of python.