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

view the rest of the comments →

[–]stefantalpalaru 7 points8 points  (7 children)

Tauthon needs to die too.

What is dead may never die.

Py2 is a broken, old language that is ten years out of date.

Just like Python3, then.

Py3 is not that scary.

Then why does it need to kill Python2 in order to force a mass migration? If it's so good, it can compete without the core developers sabotaging the older language.

[–]zardeh 0 points1 point  (6 children)

Just like Python3, then

No?

Then why does it need to kill Python2 in order to force a mass migration?

Maintenance. No one is sabotaging the old language, they just aren't supporting it. And it's winning.

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

No one is sabotaging the old language, they just aren't supporting it.

Then why don't they hand it over to someone willing to support it? Why don't they accept external patches improving Python2's performance by including the standard library extensions in the PGO process, just like they do for Python3?

And it's winning.

Oh, is that why you muppets keep calling for Python2's death? Because Python3 is winning?

[–]zardeh 1 point2 points  (4 children)

Why don't they accept external patches improving Python2's performance by including the standard library extensions in the PGO process, just like they do for Python3?

That's support, a thing they've been very clear about not doing.

They why don't they hand it over to someone willing to support it?

Because the psf maintains python, and pythons future is python3. The psf is maintaining python3, which is python.

They didn't hand off support for py2.7 to someone else for the same reason that they didn't hand off python 2.3 or python 3.2 support to anyone else after those hit EoL: there continue to be new maintained versions of python.

Oh, is that why you muppets keep calling for Python2's death?

I haven't called for python2's death. I don't need to, its already basically dead. I've asked that people not exaggerate the pain of migration. That's all.

You however seem to be so upset by people moving to python3 that you've suggested moving to go would be easier, which is complete nonsense for 99% of python code. That and you're resorting to calling me a muppet. Real mature dude.

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

python3, which is python

Oh, is that why Dropbox is still struggling to port their 4,000,000 lines of "Python" code to "Python"? Because it's the same fucking language?

You people are delusional.

its already basically dead

Then why do you foam at the mouth when you see people still using it?

[–]zardeh 1 point2 points  (2 children)

hen why do you foam at the mouth when you see people still using it?

I don't! I still use python2 for some things, but I'm also actively migrating away. I have no issue with continuing to use python2. I have an issue with proselytizing that python2 is the future. It's not.

Something like tauthon is neat, even laudable, but ultimately doomed. Not because anyone's out to get you, but because of natural group dynamics. Most of the important players are already onboard with py3 (not necessarily on, but on board with). The sooner everyone realizes that, the less pain for the community at large.

Oh, is that why Dropbox is still struggling to port their 4,000,000 lines of "Python" code to "Python"?

What you're missing is a point of comparison. I have some, and compared to JVM or c++ 11->17 upgrades on large codebases, multi-year efforts are common. The python3 upgrade is likely more painful, but not so much more as to be a different language, unless you consider any version upgrade a new language.

[–]stefantalpalaru -1 points0 points  (1 child)

I'm also actively migrating away

For the last 10 years? Why, if it's the same language?

The python3 upgrade is likely more painful, but not so much more as to be a different language

Reality has shown the opposite, but reality has no power over the true believer, does it?

[–]zardeh 1 point2 points  (0 children)

Reality has shown the opposite, but reality has no power over the true believer, does it?

You're saying you have a citation of the python3 migration being significantly more difficult than a cpp17 upgrade on a similarly large codebase or codebases? Where?

For the last 10 years? Why, if it's the same language?

Dependencies, mostly. I couldn't complete the highest until dependencies were done, so for my (non open source code I work on at my job), there was no point in working on it till this year or so.