Live data from Hacker News

Python: language moratorium is lifted

article.gmane.org

21–30 of 30 posts

Re: Python: language moratorium is lifted

#21
post #12
post #4

Earlier quoted context omitted.

So, essentially, the non-"python-is-my-second-language" crowd should wait not just for v3-as-is to gain acceptance, but until 3.3 before they start migrating, or what? From a high-level outsider perspective, the shift from 2.x to "current" looks like amateur hour.

> From a high-level outsider perspective, the shift from 2.x to "current" looks like amateur hour. You are hearing a lot of noise now , because 3.X has finally become viable enough to be interesting to the wider python community, I hope. That's why people keep hyping it. 3.0 was not ready, and only a few dedicated pythoneers (like Mark Pilgrim) pushed it. It was very professional of the python community to keep 3.X i…

I can't express how much I love the quote "It was very professional of the python community to keep 3.X in it's mother's basement until it was well-enough dressed to be seen in public." - it's incredibly spot-on.

Re: Python: language moratorium is lifted

#22
post #17

Earlier quoted context omitted.

And you don't want to use Stackless Python because ... ?

I was going to suggest that Stackless is dead, given that I haven't heard any news about it. But that would have been foolish of me: http://zope.stackless.com/Members/rmtew/News%20Archive/3.1.3

As far as I know, they haven't developed any significant new features (does it need any?) in a long long time, so in that sense it's not an "active" project. But they're usually quick to port their patchset to each new Python version.

Re: Python: language moratorium is lifted

#24
post #17

Earlier quoted context omitted.

And you don't want to use Stackless Python because ... ?

I was going to suggest that Stackless is dead, given that I haven't heard any news about it. But that would have been foolish of me: http://zope.stackless.com/Members/rmtew/News%20Archive/3.1.3

stackless is actively used by mmorpg EvE Online

Re: Python: language moratorium is lifted

#25
post #17

Earlier quoted context omitted.

And you don't want to use Stackless Python because ... ?

I was going to suggest that Stackless is dead, given that I haven't heard any news about it. But that would have been foolish of me: http://zope.stackless.com/Members/rmtew/News%20Archive/3.1.3

There is also continued work on coroutines (based on Stackless) in Pypy: http://codespeak.net/pypy/dist/pypy/doc/stackless.html

Re: Python: language moratorium is lifted

#26
post #9
post #8

Earlier quoted context omitted.

That you expound your claim with adornment and superfluous grammar obfuscates your intent to purport and diseminate the acceptation of your supposition. ... In other words, no one knows what you are talking about.

A semi-colon for a poem, really? Could I have not meant to meant to emphasize the first part of that sentence with a break while continuing the train of thought? By the way, it's 'disseminate.'

Nice try, Watson.

Re: Python: language moratorium is lifted

#28
Did anyone else think "Wow, 2 years already"? (I remember people claiming the moratorium was a signal of Python's demise...)

I'm happy about PEP 380, it seems like they might as well do PEP 3152 as well since they're highly related...

Re: Python: language moratorium is lifted

#29

Earlier quoted context omitted.

I was going to suggest that Stackless is dead, given that I haven't heard any news about it. But that would have been foolish of me: http://zope.stackless.com/Members/rmtew/News%20Archive/3.1.3

There is also continued work on coroutines (based on Stackless) in Pypy: http://codespeak.net/pypy/dist/pypy/doc/stackless.html

Thanks, I'll check this out in addition to stackless.

Re: Python: language moratorium is lifted

#30
post #22

Earlier quoted context omitted.

I was going to suggest that Stackless is dead, given that I haven't heard any news about it. But that would have been foolish of me: http://zope.stackless.com/Members/rmtew/News%20Archive/3.1.3

As far as I know, they haven't developed any significant new features (does it need any?) in a long long time, so in that sense it's not an "active" project. But they're usually quick to port their patchset to each new Python version.

It adds coroutines to Python. What more do you need? It runs every other Python package, it tracks new Python releases perfectly, which means its "significant new features" are identical to Python's significant new features.

What would an "active" version of the project look like?

Post reply on HN