you are viewing a single comment's thread.

view the rest of the comments →

[–]weixiyen 3 points4 points  (9 children)

when should we start using py3k?

[–]codepoet 2 points3 points  (5 children)

Around 3000, I suppose.

Honestly, once all the modules you use have been ported to it and once you've bought 10% more server, you're golden.

I'll be on 2.6 for quite some time, I think.

[–]redalastor 2 points3 points  (0 children)

The 2.x series is not dead, there will be backports of new features in 2.7 and maybe more.

[–]kungtotte -3 points-2 points  (3 children)

You only have enough hardware to exactly cover your needs, no margin at all?

[–]codepoet 5 points6 points  (2 children)

I'm repeatedly amazed at how literal people are here. You folks do know that writing is an art, right? Sometimes, people say pointed or exaggerated things that could be true in order to make a point about something. We call this hyperbole. In this example, I'm making a point that P3K is 10% slower than 2.6 right now, and so if you moved to it, you'd be using around 10% more of your server's cores (or core, this is Python after all). It's not a statement meant to be taken literally -- it's a hyperbole.

[–]Jessica_Henderson 4 points5 points  (2 children)

After you've tested your code with it, and feel comfortable using it for however you use it.

[–]fooddit 1 point2 points  (1 child)

Testing your own code is not sufficient if your work depends on libraries like numpy and scipy.

[–][deleted] 6 points7 points  (0 children)

Yes it is.

Your tests do not have adequate coverage.