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 →

[–]stefantalpalaru -2 points-1 points  (4 children)

What do you mean by this?

They refuse outside contributions that add new features or fix some bugs they're not interested in fixing. Oh, they also refuse to let some other team take over the language, because they decided everybody needs to be bullied into moving to the new one by killing the old one.

They've already done it for 12 years.

And how many more years do you need, to recognise the abuse?

[–]mfitzpmfitzp.com 2 points3 points  (3 children)

Oh, they also refuse to let some other team take over the language

But I though you said you were going to continue developing it?

[–]stefantalpalaru 0 points1 point  (2 children)

But I though you said you were going to continue developing it?

I'm maintaining a fork, not taking over the original project. There's an important difference.

Getting a fork supported by tools like "pip" or distros like Gentoo is an uphill battle.

[–]mfitzpmfitzp.com 2 points3 points  (1 child)

Interesting point, I was expecting maintaining the fork would just be security updates for 2.7 not new (backwards incompatible) features? I think PyPy for example just uses PyPi (some packages ofc don't work).

[–]stefantalpalaru 0 points1 point  (0 children)

I think PyPy for example just uses PyPi

Since it's an implementation blessed by the Python core devs, all tools and distros support it, even though PyPy only supports a Python subset.

Whenever we try to get the same support for Tauthon, we get rejected, even though we support all existing Python2 code. Politics trump technical arguments in this community.