On 11/22/2013 01:00 AM, Richard Tew wrote: > > [snip] > > Yet, suddenly, the chance that we may release a "Stackless Python > 2.8", is a concern. Because there is no CPython 2.8 to mirror, and we've said there will not be one. It certainly didn't help that this was presented one week before the feature freeze deadline for 3.4 and Christian stated [1] his "2.8" release was going to happen in one week unless we talked him out of it. > We're not talking about releasing a Python 2.8 against anyone's wishes > here. Having "Python 2.8" in the name is going to be a PR nightmare. Other names have been suggested. > Or in _this specific case_, doing anything other than naming > something in a way we've been naming it for over a decade. When has Stackless created a version that didn't mirror the CPython version? If you haven't, then you are doing something different. > That there are people who would consider using the trademark to force > us to change the name we've been using without harm for 14 years, > worries me. This concern came about because of the misapprehension that the name would be "Python 2.8" with no "Stackless" in front. -- ~Ethan~ [1] https://mail.python.org/pipermail/python-dev/2013-November/130437.html
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4