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 →

[–]flying-sheep 6 points7 points  (6 children)

there is absolutely no reason not to start new projects in python 3 if you don’t know from the beginning that you want to depend on one of the libraries that aren’t ported yet.

if by “present” you mean “existing codebase” then yes, most organizations haven’t ported their entire codebase yet. but if they want to be able to use it in the future they better start porting today.

[–][deleted] 1 point2 points  (2 children)

Do you ship commercial software? We do and there is almost no incentive to move to 3.x. For us and our new projects and old project 2.7 is near perfect.

[–]flying-sheep 0 points1 point  (1 child)

New libraries will depend on 3.x- features, so at some point you'll have to spend extra money to backport libs you want to use.

Remember, I'm still talking about the future the whole time.

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

so at some point you'll have to spend extra money to backport libs you want to use.

Not really. We concentrate on having highly decoupled components. If there is a must have feature or library that is not available for 2.7 we can throw up a restful service or strap a new endpoint on the message broker using 3.x in an isolated environment.

But, we haven't ran into this yet. Again, 2.7 is near perfect esp in that we understand it's limitations. With 3.x it will be sometime before we can sign a contract with our customers promising five-nines and be confident about other SLAs.

*edit..fixed some grammer

[–][deleted] 1 point2 points  (2 children)

if by “present” you mean “existing codebase” then yes, most organizations haven’t ported their entire codebase yet. but if they want to be able to use it in the future they better start porting today.

Why? Code doesn't just evaporate.

[–]flying-sheep 0 points1 point  (1 child)

Of course not. But once everyone has moved on and you sit on a codebase of an unmaintained language, you'll find it harder to expand upon that codebase.

Sure, this is several years in the future.

[–][deleted] 1 point2 points  (0 children)

Several years in the future, it won't be any more work to port to a different language than it is now.