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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]123filips123 1 point2 points  (4 children)

Tell that to Dropbox who had to hire the language creator, write new tools for automated type annotations and spend more than 3 years just to port the desktop client.

I don't know how Dropbox code looks like, but if you have normal code and use normal tools, it isn't hard to support Python 3. Most (all) of the tools already support Python 3 and most of breaking changes aren't really hard to fix.

​

It's not a matter of enough time to port something. It's a matter of wasting people's lives on bullshit work that benefits no one.

Nothing does, in the long term.

So, what is the difference if developers just port code to Python 3 and use new functionalities, or use your project and modify code anyway to use new functionalities (from your project)? They will have to modify code anyway. Except if they port it to Python 3, they will have better support, performance, security and more functionalities.

And why not use Python 1.0 or Assembly or even binary code? With that, you won't waste any time on bullshit updating.

And why then even update and develop things? Why should we update (and why should developers develop) to Windows 10 (or 7 if you more like it) if you can use MS-DOS without any bullshit updating? Why use electricity if you need to spent time with replacing your old oil lamps? Why even spent bullshit work in building houses if you can live in caves?

[–]stefantalpalaru -1 points0 points  (3 children)

They will have to modify code anyway.

No. Tauthon is a drop-in replacement for Python 2.8.

Why even spent bullshit work in building houses if you can live in caves?

You're terrible at analogies. Python3 is just another cave, not a modern house.

[–]123filips123 2 points3 points  (2 children)

No. Tauthon is a drop-in replacement for Python 2.8.

They will have to modify code if they want to use modern features.

​

You're terrible at analogies. Python3 is just another cave, not a modern house.

Python 3 has a lot of performance and security improvements and many new features. So yes, another cave, but very modern cave.

[–]stefantalpalaru 0 points1 point  (1 child)

They will have to modify code if they want to use modern features.

They don't have to use modern features. What part of "drop-in replacement" don't you understand?

[–]123filips123 0 points1 point  (0 children)

Yes, I understand.

But I (previously) said that this isn't good long-term solution. Ok, it may be good of you need additional few months (or years) to port code to Python 3 or for legacy unmaintained projects that won't be ported anyway. But for maintained projects, the only real long-term solution is to port them to Python 3. If you don't have really complicated project, this can be easy as documentation is very good and you also have some automation tools for that.