Rename this Project

[flying-sheep]

The current name might confuse people into thinking this was an official port, filing bugs on the official bug tracker for it and so on.

There will never be an official Python 2.8, so there should never be something called “Python 2.8” or similar.

@gvanrossum might confirm this if you don't believe my words.

[flying-sheep]

I basically just filed an issue for what people in this thread were saying

[flying-sheep]

I basically just filed an issue for what people in this thread were saying

[nirs]

Cpython maintainers has abandoned python 2 and the community. I don't see an issue with this name.

Maybe python 3 should change its name, as distriburions are planing to ship python3 as python, breaking good python code assuming that python executable can run python code.

[nirs]

Cpython maintainers has abandoned python 2 and the community. I don't see an issue with this name.

Maybe python 3 should change its name, as distriburions are planing to ship python3 as python, breaking good python code assuming that python executable can run python code.

[flying-sheep]

I’m sorry you feel that way, but what you say is not, in fact, the truth. Python 3 is just the next version of the language, announced ~10 years ago. All the time, it was clear Python 2 was going to be deprecated and discontinued eventually, just like Python 1, Java 4, and Lua 5.2.

People had 8 years to make their unit tests run with Python 3. I don’t know what led to the misconception that Python 2 was going to stick around unlike every deprecated version of any language or software ever.

There was no abandonment of any community, just a bunch of people deciding to defer eliminating technical debt while rationalizing that decision by forming a weird emotional attachment to some programming language’s old version.

[flying-sheep]

I’m sorry you feel that way, but what you say is not, in fact, the truth. Python 3 is just the next version of the language, announced ~10 years ago. All the time, it was clear Python 2 was going to be deprecated and discontinued eventually, just like Python 1, Java 4, and Lua 5.2.

People had 8 years to make their unit tests run with Python 3. I don’t know what led to the misconception that Python 2 was going to stick around unlike every deprecated version of any language or software ever.

There was no abandonment of any community, just a bunch of people deciding to defer eliminating technical debt while rationalizing that decision by forming a weird emotional attachment to some programming language’s old version.

[yan12125]

At least this line should be at the first line: This is not an official Python release; see PEP 404, not in the bottom

[yan12125]

At least this line should be at the first line: This is not an official Python release; see PEP 404, not in the bottom

[flying-sheep]

By the way: If this project gets people to port more easily then I’m all for it!

But the PSF owns the name Python, so unless they decide to adopt this project (which very likely won’t happen because of PEP 404), this project can’t keep its name.

[flying-sheep]

By the way: If this project gets people to port more easily then I’m all for it!

But the PSF owns the name Python, so unless they decide to adopt this project (which very likely won’t happen because of PEP 404), this project can’t keep its name.

[ncoghlan]

Firstly, thanks for taking on the task of creating a hybrid superset of Python 2 that incorporates features you find interesting! Allowing folks to vote with their time and energy and create the projects and remixes that they wish existed is exactly the kind of thing that open source licensing is designed to allow.

However, as others have noted above, the PSF does have various policies specifically around the use of the Python mark, and the Trademarks Committee are reviewing the question of whether or not the current name of the project is appropriate in that light.

There's precedent for Python subsets and variants using the term as part of a longer name (e.g. MicroPython, Stackless Python), so something like "HybridPython" would be more likely to pass muster than an unqualified "Python".

Alternatively, a name like NorwegianBlue would reference Guido's original inspiration for the name of the language, while completely steering clear of any possible trademark concerns.

[ncoghlan]

Firstly, thanks for taking on the task of creating a hybrid superset of Python 2 that incorporates features you find interesting! Allowing folks to vote with their time and energy and create the projects and remixes that they wish existed is exactly the kind of thing that open source licensing is designed to allow.

However, as others have noted above, the PSF does have various policies specifically around the use of the Python mark, and the Trademarks Committee are reviewing the question of whether or not the current name of the project is appropriate in that light.

There's precedent for Python subsets and variants using the term as part of a longer name (e.g. MicroPython, Stackless Python), so something like "HybridPython" would be more likely to pass muster than an unqualified "Python".

Alternatively, a name like NorwegianBlue would reference Guido's original inspiration for the name of the language, while completely steering clear of any possible trademark concerns.

[dw]

I'm really happy to see a project like this gain a little traction, and I truly hope it succeeds as I'm certainly not the first or hundredth person to think something like it might be a good idea.

For that reason, and since currently it looks like @naftaliharris is the only developer, spending the limited energy available on an unwinnable trademark issue probably would not be wise.

+1 for changing the project name to something distinct, but it would also be great if the installed binaries and libraries maintained the same interface as official Python, since I think renames there would impact the project's usefulness.

[dw]

I'm really happy to see a project like this gain a little traction, and I truly hope it succeeds as I'm certainly not the first or hundredth person to think something like it might be a good idea.

For that reason, and since currently it looks like @naftaliharris is the only developer, spending the limited energy available on an unwinnable trademark issue probably would not be wise.

+1 for changing the project name to something distinct, but it would also be great if the installed binaries and libraries maintained the same interface as official Python, since I think renames there would impact the project's usefulness.

[flying-sheep]

it would also be great if the installed binaries and libraries maintained the same interface as official Python

sure, just not $prefix/bin/python2.8

[flying-sheep]

it would also be great if the installed binaries and libraries maintained the same interface as official Python

sure, just not $prefix/bin/python2.8

[gvanrossum]

Since I was asked: The project's name (and its binary name) need to change. They are misleading. The rest looks acceptable according to Python's license. This is not an endorsement (far from it).

[gvanrossum]

Since I was asked: The project's name (and its binary name) need to change. They are misleading. The rest looks acceptable according to Python's license. This is not an endorsement (far from it).

[tiran]

Please also change the name of any helper scripts, the name of the shared library/DLL and the include directory. The name of the header file Python.h can probably stay since it's part of the public API.

• /usr/bin/python
• /usr/bin/python2.8
• /usr/bin/python-config
• /usr/bin/python2.8-config
• /usr/lib/libpython*
• /usr/include/python2.8

[tiran]

Please also change the name of any helper scripts, the name of the shared library/DLL and the include directory. The name of the header file Python.h can probably stay since it's part of the public API.

• /usr/bin/python
• /usr/bin/python2.8
• /usr/bin/python-config
• /usr/bin/python2.8-config
• /usr/lib/libpython*
• /usr/include/python2.8

[stefantalpalaru]

I'll write a Gentoo ebuild for this package, as soon as you settle on a new name for it.

[stefantalpalaru]

I'll write a Gentoo ebuild for this package, as soon as you settle on a new name for it.

[dbohdan]

If you're going to change the project's name, let me suggest some short, Monty Python-themed options.

• Pythonesque (/usr/bin/pesque)
• Reunion
• Cleese
• Brian
• Wanda
• Nudge
• Rabbit
• Brazil

[dbohdan]

If you're going to change the project's name, let me suggest some short, Monty Python-themed options.

• Pythonesque (/usr/bin/pesque)
• Reunion
• Cleese
• Brian
• Wanda
• Nudge
• Rabbit
• Brazil

[stefantalpalaru]

How about "py2", taking a hint from "pypy"?

[stefantalpalaru]

How about "py2", taking a hint from "pypy"?

[giampaolo]

"py28"?

[giampaolo]

"py28"?

[stefantalpalaru]

Why also freeze the minor version? It's perfectly possible that a 2.9.x will be released at some point.

[stefantalpalaru]

Why also freeze the minor version? It's perfectly possible that a 2.9.x will be released at some point.

[trevyn]

"p"

[trevyn]

"p"

[paul-nechifor]

Sadly, P is taken: http://esolangs.org/wiki/P .

[paul-nechifor]

Sadly, P is taken: http://esolangs.org/wiki/P .

[trevyn]

Looks abandoned, site is down and everything.

[trevyn]

Looks abandoned, site is down and everything.

[maedoc]

Since both 2 and 3 features are handled you might consider six (I'm aware that's also the name of a compatibility package).

[maedoc]

Since both 2 and 3 features are handled you might consider six (I'm aware that's also the name of a compatibility package).

[naftaliharris]

I don't mind renaming this project. Any other suggestions for good names? I personally like "Pythonesque (/usr/bin/pesque)" the best so far, thanks @dbohdan! :-)

@VanL, not that I'm necessarily picking that, but would a name like that be acceptable?

[naftaliharris]

I don't mind renaming this project. Any other suggestions for good names? I personally like "Pythonesque (/usr/bin/pesque)" the best so far, thanks @dbohdan! :-)

@VanL, not that I'm necessarily picking that, but would a name like that be acceptable?

[kirbyfan64]

Brydge? Since it's"between" 2 and 3...

Ok, I'll leave now.

[kirbyfan64]

Brydge? Since it's"between" 2 and 3...

Ok, I'll leave now.

[teles]

Change the name for snake 🐍 !

[teles]

Change the name for snake 🐍 !

[nirs]

Maybe nython for "nython is not official python"? or for "Naftali's Python"?

[nirs]

Maybe nython for "nython is not official python"? or for "Naftali's Python"?

[degaart]

"snek", please name it "snek"!!!!

[degaart]

"snek", please name it "snek"!!!!

[JulienPalard]

Still Monty Python inspired: pysant, pronounced "peasant"? (Or present you choose).

A what?
A present!
A what???
A present!
A what???
Un cadeau !
Ahhhh, "a present"!

[JulienPalard]

Still Monty Python inspired: pysant, pronounced "peasant"? (Or present you choose).

A what?
A present!
A what???
A present!
A what???
Un cadeau !
Ahhhh, "a present"!

[dubberx]

I like @teles name-of-a-snake idea. What about

• kraithon

, blending krait and python (krait, family of snakes, rhymes with "kite")?

[dubberx]

I like @teles name-of-a-snake idea. What about

• kraithon

, blending krait and python (krait, family of snakes, rhymes with "kite")?

[ojn]

Just remove the h - Pyton or call it Flying Circus.

[ojn]

Just remove the h - Pyton or call it Flying Circus.

[naftaliharris]

Pyton

Heh. I actually mess this up so often that I alias this on my machine to "python": https://github.com/naftaliharris/dotfiles/blob/master/.bashrc#L151

[naftaliharris]

Pyton

Heh. I actually mess this up so often that I alias this on my machine to "python": https://github.com/naftaliharris/dotfiles/blob/master/.bashrc#L151

[ojn]

As I think about it, Monty would be a cool name...

[ojn]

As I think about it, Monty would be a cool name...

[mrabarnett]

As it's Python 2, how about DuoPython?

[mrabarnett]

As it's Python 2, how about DuoPython?

[naftaliharris]

As I think about it, Monty would be a cool name...

It's taken, bummer... http://montyscoconut.github.io/

[naftaliharris]

As I think about it, Monty would be a cool name...

It's taken, bummer... http://montyscoconut.github.io/

[ncoghlan]

@naftaliharris Thanks for being responsive to the name change request!

Assuming it is able to obtain the PSF's blessing from a trademark perspective, @dbohdan's suggestion of Pythonesque (pesque) sounds promising to me, as the main benefit of the project lies in it being Python-like, without being 100% constrained to meeting any specific version of the language definition (in particular, combining syntactic and runtime features of Python 3 with the Python 2 core data model).

[ncoghlan]

@naftaliharris Thanks for being responsive to the name change request!

Assuming it is able to obtain the PSF's blessing from a trademark perspective, @dbohdan's suggestion of Pythonesque (pesque) sounds promising to me, as the main benefit of the project lies in it being Python-like, without being 100% constrained to meeting any specific version of the language definition (in particular, combining syntactic and runtime features of Python 3 with the Python 2 core data model).

[naftaliharris]

Thanks for being responsive to the name change request!

Of course @ncoghlan. :-)

Off topic, but I've just got to say I'm a huge fan of yours. As you'd imagine when working on this I read a lot of your code and writing, and have a ton of respect for the work you've done for the Python community over the last 10+ years. You should be very very proud.

[naftaliharris]

Thanks for being responsive to the name change request!

Of course @ncoghlan. :-)

Off topic, but I've just got to say I'm a huge fan of yours. As you'd imagine when working on this I read a lot of your code and writing, and have a ton of respect for the work you've done for the Python community over the last 10+ years. You should be very very proud.

[ntoll]

May I suggest "Parrot"..?

Why?

1. It's not dead, it's just... etc... (appropriate Monty Python reference).
2. It's still an animal.
3. It's not a Python.

Potential issue: doesn't PERL have a parrot VM? Might be too close...?

[ntoll]

May I suggest "Parrot"..?

Why?

1. It's not dead, it's just... etc... (appropriate Monty Python reference).
2. It's still an animal.
3. It's not a Python.

Potential issue: doesn't PERL have a parrot VM? Might be too close...?

[flying-sheep]

Yeah, parrot is probably not a good fit for that reason.

Someone suggested using the breed of parrot used in the sketch (Norwegian blue), but that reference might be too obscure.

“pesque” sounds a bit too much like “pesky” IMHO.

[flying-sheep]

Yeah, parrot is probably not a good fit for that reason.

Someone suggested using the breed of parrot used in the sketch (Norwegian blue), but that reference might be too obscure.

“pesque” sounds a bit too much like “pesky” IMHO.

[meiralins]

I would call it Phyton.

[meiralins]

I would call it Phyton.

[pfalcon]

Given that the project poses itself as an implementation of https://www.python.org/dev/peps/pep-0404/ ("Python 2.8 Un-release Schedule") , a logical name would be "Unpython".

[pfalcon]

Given that the project poses itself as an implementation of https://www.python.org/dev/peps/pep-0404/ ("Python 2.8 Un-release Schedule") , a logical name would be "Unpython".

[ncoghlan]

Regarding the command name to pair up with the suggestion of "Pythonesque", pyesque occurred to me as a potentially clearer option than pesque - it has the py prefix (suggesting Python), and avoids the similarity to "pesky" that @flying-sheep mentioned.

[ncoghlan]

Regarding the command name to pair up with the suggestion of "Pythonesque", pyesque occurred to me as a potentially clearer option than pesque - it has the py prefix (suggesting Python), and avoids the similarity to "pesky" that @flying-sheep mentioned.

[avamsi]

How about Pythold?

^{Okay, I'll get out of here now.}

[avamsi]

How about Pythold?

^{Okay, I'll get out of here now.}

[cndreisbach]

The wonambi is an extinct Australian snake species. While it was not a python, it was a constrictor. The name wonambi refers to the mythological Rainbow Serpent of the Dreamtime. Wonambi(s?) were around 6 meters long, making it a very large and terrifying snake.

Anyway, the name of a extinct constrictor seems pretty appropriate and badass for this resurrection of an extinct Python.

[cndreisbach]

The wonambi is an extinct Australian snake species. While it was not a python, it was a constrictor. The name wonambi refers to the mythological Rainbow Serpent of the Dreamtime. Wonambi(s?) were around 6 meters long, making it a very large and terrifying snake.

Anyway, the name of a extinct constrictor seems pretty appropriate and badass for this resurrection of an extinct Python.

[sibayanjasper]

I suggest

• dpy - Discontinued python
• opy - Overhauled python
• vyper - "viper" another snake but with "y" for familiarity

[sibayanjasper]

I suggest

• dpy - Discontinued python
• opy - Overhauled python
• vyper - "viper" another snake but with "y" for familiarity

[chainsawriot]

Python 2.8 is not okay then just call it twoeight.

[chainsawriot]

Python 2.8 is not okay then just call it twoeight.

[alanjds]

I would like to adopt Py3 if it does not break my Py2 code. The 2to3 tool is less helpful than a 3to2 one. What I dream is a way to code 3 along with existing 2. Backport and derived is what sticks on my mind, but the ideas of merged, along, bridge and feasible gives me future-related smiles.

MergedPython
AlongPython
AlonguedPython (longer Py2 snake life)
BackFromFuturePy (bffpython2.8 is a ready joke)
BackToTheFuturePy (ok. This is a bad one)
NewOldPython (for now on, no p0rn-related names)

The ideas or this being what we want but not what PSF want are still fresh

LostPython
DeprecatedPython
UnwantedPython
WantedPython (we want alive, they want dead)
DissidentPython

But to be really fair, this would be a short-lived necessity until something else cames, like a yet to be written bytecode transpiler got wrote

PythonSkin (only the past echo of a new snake)
YetwoPython
NothreePython

And to finish, I liked backpy until a remind of Trump and old and new clashing and hate and flames. I want to see a future good for both people. A future where the same BothPython runs Python2 unmodified code for py2 people and Python3 unmodified code for py3 people.

BothPython !

[alanjds]

I would like to adopt Py3 if it does not break my Py2 code. The 2to3 tool is less helpful than a 3to2 one. What I dream is a way to code 3 along with existing 2. Backport and derived is what sticks on my mind, but the ideas of merged, along, bridge and feasible gives me future-related smiles.

MergedPython
AlongPython
AlonguedPython (longer Py2 snake life)
BackFromFuturePy (bffpython2.8 is a ready joke)
BackToTheFuturePy (ok. This is a bad one)
NewOldPython (for now on, no p0rn-related names)

The ideas or this being what we want but not what PSF want are still fresh

LostPython
DeprecatedPython
UnwantedPython
WantedPython (we want alive, they want dead)
DissidentPython

But to be really fair, this would be a short-lived necessity until something else cames, like a yet to be written bytecode transpiler got wrote

PythonSkin (only the past echo of a new snake)
YetwoPython
NothreePython

And to finish, I liked backpy until a remind of Trump and old and new clashing and hate and flames. I want to see a future good for both people. A future where the same BothPython runs Python2 unmodified code for py2 people and Python3 unmodified code for py3 people.

BothPython !

[Bl41r]

Has Crython been taken?

[Bl41r]

Has Crython been taken?

[senyai]

You all guys know 'the Knights who say "Ni!"', right? Guess what the element number of Ni is in periodic table? 28! So let's say Ni! to python 3, and run nipyton.

[senyai]

You all guys know 'the Knights who say "Ni!"', right? Guess what the element number of Ni is in periodic table? 28! So let's say Ni! to python 3, and run nipyton.

[ei-grad]

It also means "neither" in ukranian.

[ei-grad]

It also means "neither" in ukranian.

[conradsnicta]

@naftaliharris - Nice and useful project :) Some suggestions for the name, which would send a clear message: it's close to Python without being the so-called "official" Python:

• pithon
• piethon
• bython
• repy28 or simply repy (where the re is for retro, ironically stated)

[conradsnicta]

@naftaliharris - Nice and useful project :) Some suggestions for the name, which would send a clear message: it's close to Python without being the so-called "official" Python:

• pithon
• piethon
• bython
• repy28 or simply repy (where the re is for retro, ironically stated)

[mirabilos]

Nothing with py in it, that’s already mostly used by packages for Python.

“Pyesque” (even “pesque”) is very hard to pronounce for Germans (for example); I’d not have such objections with “snek” (which also made me laugh).

Please recherche in Debian unstable beforehand whether the name is taken by any package, as otherwise, Debian will not allow it in unrenamed (node.js was renamed from node to nodejs because “node” was taken by an Amateur Radio program widely deployed in remote locations and over a decade older, for example).

[mirabilos]

Nothing with py in it, that’s already mostly used by packages for Python.

“Pyesque” (even “pesque”) is very hard to pronounce for Germans (for example); I’d not have such objections with “snek” (which also made me laugh).

Please recherche in Debian unstable beforehand whether the name is taken by any package, as otherwise, Debian will not allow it in unrenamed (node.js was renamed from node to nodejs because “node” was taken by an Amateur Radio program widely deployed in remote locations and over a decade older, for example).

[naftaliharris]

Please recherche in Debian unstable beforehand whether the name is taken by any package, as otherwise, Debian will not allow it in unrenamed

Thanks for that!

[naftaliharris]

Please recherche in Debian unstable beforehand whether the name is taken by any package, as otherwise, Debian will not allow it in unrenamed

Thanks for that!

[miraculixx]

@gvanrossum the world has an abundance of "technically superior" projects that went nowhere... wat we need is solutions that work, and this project is clearly on the right track. yea

[miraculixx]

@gvanrossum the world has an abundance of "technically superior" projects that went nowhere... wat we need is solutions that work, and this project is clearly on the right track. yea

[elkarouh]

Name suggestion: Python2++

[elkarouh]

Name suggestion: Python2++

[RecklessProcedure]

I'm all for this. I despise Python3 for a number of reasons. Ever have a reason to compile Python from scratch? When you try to build Python3: "Error: G++ required" "Test suite must be run from an xterminal". So much for a system with only cross-compiled C and/or anyone running without Xorg. Such nonsense decisions by the Py3 team, the worst of which was a decision to re-implement rather than extend in more Unicode friendly ways. Shovel the work onto your users.

Anyway, about the name: Typhon is an anagram of the name. Thypon is another, with a slightly Monte sound.

[RecklessProcedure]

I'm all for this. I despise Python3 for a number of reasons. Ever have a reason to compile Python from scratch? When you try to build Python3: "Error: G++ required" "Test suite must be run from an xterminal". So much for a system with only cross-compiled C and/or anyone running without Xorg. Such nonsense decisions by the Py3 team, the worst of which was a decision to re-implement rather than extend in more Unicode friendly ways. Shovel the work onto your users.

Anyway, about the name: Typhon is an anagram of the name. Thypon is another, with a slightly Monte sound.

[tiran]

Well, this discussion hit rock bottom with fake news and false accusations.

[tiran]

Well, this discussion hit rock bottom with fake news and false accusations.

[pfalcon]

Also, stats: during the last month (which generally should be prolific at least in the number of people poked with it, due to holidays), 3 people contributed commits, 23 the maintainer and 2 other people contributed a commit each. So, importance and usefulness of this project seems to be overrated. This is a cute pet project for @naftaliharris , and he can be only wished best of luck with it, and so far he chose the right name for the project: "placeholder" is confusing, but the whole project is confusing, so naming is on par.

[pfalcon]

Also, stats: during the last month (which generally should be prolific at least in the number of people poked with it, due to holidays), 3 people contributed commits, 23 the maintainer and 2 other people contributed a commit each. So, importance and usefulness of this project seems to be overrated. This is a cute pet project for @naftaliharris , and he can be only wished best of luck with it, and so far he chose the right name for the project: "placeholder" is confusing, but the whole project is confusing, so naming is on par.

[kirbyfan64]

@tiran

Well, this discussion hit rock bottom with fake news and false accusations.

Words of truth right there...

[kirbyfan64]

@tiran

Well, this discussion hit rock bottom with fake news and false accusations.

Words of truth right there...

[alanjds]

A placeholder between Python 2 and Python 3 is nice for me. Just have no clue that it is a Python-related thing.

plyceholder ?

[alanjds]

A placeholder between Python 2 and Python 3 is nice for me. Just have no clue that it is a Python-related thing.

plyceholder ?

[RecklessProcedure]

As to fake news and false accusations: All of that I see is people coming here to make some kind of trouble or discouraging remark about someone trying to keep 2.x alive. What motivates them is irrelevant, conspiracy or not. But, as much as I'd like to see 2.x keep going, I largely do not care. Why? Because the 2/3 debacle has caused me no small amount of trouble. As such, I've ruled the language out as a whole for anything but small scripts going forward and... I'm not the only one to do so.

[RecklessProcedure]

As to fake news and false accusations: All of that I see is people coming here to make some kind of trouble or discouraging remark about someone trying to keep 2.x alive. What motivates them is irrelevant, conspiracy or not. But, as much as I'd like to see 2.x keep going, I largely do not care. Why? Because the 2/3 debacle has caused me no small amount of trouble. As such, I've ruled the language out as a whole for anything but small scripts going forward and... I'm not the only one to do so.

[kirbyfan64]

I'm going to humbly suggest that @naftaliharris lock this issue, because at this point it's mostly people suggesting random names (too many to search through) or people yelling "omg python three suxx" or "omg dis project is stuupidz" or other random crap...

[kirbyfan64]

I'm going to humbly suggest that @naftaliharris lock this issue, because at this point it's mostly people suggesting random names (too many to search through) or people yelling "omg python three suxx" or "omg dis project is stuupidz" or other random crap...

[pfalcon]

someone trying to keep 2.x alive

The Python release team keeps 2.x alive. They do that for 16 years. Nobody was able to beat them at that so far. Only 2.7.x series is kept alive for 6 years, with current release being 2.7.13.

I'm not the only one to do so.

You aren't. But everyone else either keeps using 2.x or have switched to 3.x over last 9 years. (Supporting both ain't rocket science either, though with Python3 being available for long time everywhere, there's little point to do so for new projects.) And there's hard to talk about discouragement of projects like this - Python community has always been, and always will be prolific - it's not like other languages, where there's barely a couple of implementations. Stackless Python, Unladen Swallow, Nuitka, PyPy, Pyston, Grumpy, and many of others, including bunch to come. It's just matter of fact that some of these implementations are used less than others, and some even get abandoned.

[pfalcon]

someone trying to keep 2.x alive

The Python release team keeps 2.x alive. They do that for 16 years. Nobody was able to beat them at that so far. Only 2.7.x series is kept alive for 6 years, with current release being 2.7.13.

I'm not the only one to do so.

You aren't. But everyone else either keeps using 2.x or have switched to 3.x over last 9 years. (Supporting both ain't rocket science either, though with Python3 being available for long time everywhere, there's little point to do so for new projects.) And there's hard to talk about discouragement of projects like this - Python community has always been, and always will be prolific - it's not like other languages, where there's barely a couple of implementations. Stackless Python, Unladen Swallow, Nuitka, PyPy, Pyston, Grumpy, and many of others, including bunch to come. It's just matter of fact that some of these implementations are used less than others, and some even get abandoned.

[hadrianw]

Name proposal: February Python (as it is between 27 and 30 having only 28 or 29 days)

Variations: pyfebruary, Eternal February (eterfeb), Fybruar, February Edition

But placholder is nice as it is.

Disclaimer: I do not have horses in this race.

[hadrianw]

Name proposal: February Python (as it is between 27 and 30 having only 28 or 29 days)

Variations: pyfebruary, Eternal February (eterfeb), Fybruar, February Edition

But placholder is nice as it is.

Disclaimer: I do not have horses in this race.

[dhj-io]

My favorites so far --

nipy : Ni Python (from @senyai )
zython : The last py you'll need (from @paul-nechifor )
pystasis, pyfrost : good indication of support for fixes with no breaking changes (from @ncoghlan )
monty : great one for obvious reasons. maybe the student project would be cool with it (from @ojn )
pyclassic : reminiscent of when coca-cola fixed their mistake.

[dhj-io]

My favorites so far --

nipy : Ni Python (from @senyai )
zython : The last py you'll need (from @paul-nechifor )
pystasis, pyfrost : good indication of support for fixes with no breaking changes (from @ncoghlan )
monty : great one for obvious reasons. maybe the student project would be cool with it (from @ojn )
pyclassic : reminiscent of when coca-cola fixed their mistake.

[mvasilkov]

I kinda like the name Placeholder.

As for the binaries, they can be e.g. prefixed with p: /usr/local/bin/ppython

[mvasilkov]

I kinda like the name Placeholder.

As for the binaries, they can be e.g. prefixed with p: /usr/local/bin/ppython

[sergey-salnikov]

Ex-Ex-Parrot (/usr/bin/xxp)?

[sergey-salnikov]

Ex-Ex-Parrot (/usr/bin/xxp)?

[ojn]

As @ncoghlan mentioned, asciipy describes the project nicely. PSF would probably also allow asciiPython name since it's clear that it is a different python implementation.

[ojn]

As @ncoghlan mentioned, asciipy describes the project nicely. PSF would probably also allow asciiPython name since it's clear that it is a different python implementation.

[omeid]

bython as in, Backported Python?

[omeid]

bython as in, Backported Python?

[mirabilos]

Nothing with py- or alluring to python, to avoid confusion.

[mirabilos]

Nothing with py- or alluring to python, to avoid confusion.

[stefantalpalaru]

When you decide on a name, this should help you find the places that need to be edited: https://github.com/stefantalpalaru/gentoo-overlay/blob/master/dev-lang/py28/files/py28-rename.patch

Some "python2.8" symlinks are needed so existing autotools setups work unmodified, but that's more of a distro packager issue. On Gentoo I'm getting away with only:

/usr/lib64/python2.8
/usr/lib64/libpython2.8.a
/usr/lib64/libpython2.8.so

later edit: Gentoo package renamed; the mentioned patch is now at https://github.com/stefantalpalaru/gentoo-overlay/blob/master/dev-lang/tauthon/files/tauthon-rename.patch

[stefantalpalaru]

When you decide on a name, this should help you find the places that need to be edited: https://github.com/stefantalpalaru/gentoo-overlay/blob/master/dev-lang/py28/files/py28-rename.patch

Some "python2.8" symlinks are needed so existing autotools setups work unmodified, but that's more of a distro packager issue. On Gentoo I'm getting away with only:

/usr/lib64/python2.8
/usr/lib64/libpython2.8.a
/usr/lib64/libpython2.8.so

later edit: Gentoo package renamed; the mentioned patch is now at https://github.com/stefantalpalaru/gentoo-overlay/blob/master/dev-lang/tauthon/files/tauthon-rename.patch

[denysvitali]

To be honest, I quite like "placeholder" as a name

[denysvitali]

To be honest, I quite like "placeholder" as a name

[sibayanjasper]

I suggest

• dpy - Discontinued python
• opy - Overhauled python (sounds like o-pie)
• vyper - "viper" another snake but with "y" for familiarity

• senpy - notice me
• pynest

[sibayanjasper]

I suggest

• dpy - Discontinued python
• opy - Overhauled python (sounds like o-pie)
• vyper - "viper" another snake but with "y" for familiarity

• senpy - notice me
• pynest

[hashbackup]

Suggestion: py

It's short & obviously not a trademark infringement on Python

[hashbackup]

Suggestion: py

It's short & obviously not a trademark infringement on Python

[perennialmind]

I know placeholder is py 2.x, not pi × 2, but what about tauthon in the spirit of the Tau Manifesto? It's cheeky and fits the contrarian viewpoint.

[perennialmind]

I know placeholder is py 2.x, not pi × 2, but what about tauthon in the spirit of the Tau Manifesto? It's cheeky and fits the contrarian viewpoint.

[mrabarnett]

"py" is already used by Python as a launcher.

[mrabarnett]

"py" is already used by Python as a launcher.

[naftaliharris]

I know placeholder is py 2.x, not pi × 2, but what about tauthon in the spirit of the Tau Manifesto?

Perfect perfect PERFECT! :-D

• 6.28: six, like the six module. 28, as in PEP 404.
• pi -> tau, like e.g. C -> C++
• Two syllables, easy to say.
• Domain name is open, (though not anymore!)
• No debian packages of the same name.
• No other projects of the same name
• Obviously not an official python release.
• "It's cheeky and fits the contrarian viewpoint."

"tauthon" is the new and permanent name of this project.

Thanks @perennialmind!

[naftaliharris]

I know placeholder is py 2.x, not pi × 2, but what about tauthon in the spirit of the Tau Manifesto?

Perfect perfect PERFECT! :-D

• 6.28: six, like the six module. 28, as in PEP 404.
• pi -> tau, like e.g. C -> C++
• Two syllables, easy to say.
• Domain name is open, (though not anymore!)
• No debian packages of the same name.
• No other projects of the same name
• Obviously not an official python release.
• "It's cheeky and fits the contrarian viewpoint."

"tauthon" is the new and permanent name of this project.

Thanks @perennialmind!

[naftaliharris]

Thanks a lot to everyone who suggested names--they were uniformly better than my ideas. You're all a lot more talented than me at this, apparently. :-)

Next up, PR to change the name!

[naftaliharris]

Thanks a lot to everyone who suggested names--they were uniformly better than my ideas. You're all a lot more talented than me at this, apparently. :-)

Next up, PR to change the name!

[ncoghlan]

math.tau just landed in 3.6 as well :)

Very cool idea @perennialmind, and thanks once again for being such a good sport about finding a new name, @naftaliharris!

[ncoghlan]

math.tau just landed in 3.6 as well :)

Very cool idea @perennialmind, and thanks once again for being such a good sport about finding a new name, @naftaliharris!

[naftaliharris]

math.tau just landed in 3.6 as well :)

Ha, well tauthon definitely has to have this too!

thanks once again for being such a good sport about finding a new name, @naftaliharris!

Of course. :-)

@ncoghlan, I have a small patch for a minor traceback bug in 2.7 I wanted to contribute upstream. http://bugs.python.org/issue29107 Any advice on getting a review? Just ping the watchers again?

[naftaliharris]

math.tau just landed in 3.6 as well :)

Ha, well tauthon definitely has to have this too!

thanks once again for being such a good sport about finding a new name, @naftaliharris!

Of course. :-)

@ncoghlan, I have a small patch for a minor traceback bug in 2.7 I wanted to contribute upstream. http://bugs.python.org/issue29107 Any advice on getting a review? Just ping the watchers again?