5 ms·
Unladen Swallow: Python 3’S Best Feature
- henryl 17y agohttp://twitter.com/gvanrossum/status/7464557748 http://twitter.com/gvanrossum/status/7464557748 BDFL likes
- ptn 17y agoWhat does SGTM stand for?
- hyperbovine 17y agoI imagine BDFL would do anything at this point to get Py3k jumpstarted.
- icey 17y agoUp until now, it didn't seem like there were that many compelling reasons to try to jump to Python 3 - most of the changes were for correctness. Something like this gives a tangible reason to at least consider the pain of a major upgrade.
- jnoller 17y agoThat assumes any of us (BDFL included) are desperate to get it in production Right Now, which isn't true. However, backwards incompatibility is a tough pill to swallow and while Py3k is a cleaner, saner language it has still been a tough sell. This should give it a helpful kick in the pants.
- sophacles 17y agoI honestly thought py3k wasnt being sold. As of the last pycon, there was a lot of talk of 'slow and steady py3k adoption'. The general roadmap assumed by most people I interact with is: at some point someone will make a killer feature with py3k and that will be the tipping point. Until then, 2.x doesn't stop being awesome just cuz 3 around.
- dschobel 17y agoWhat is the killer app for python though? Django? numpy? I don't think it really has one, certainly not like the ruby/rails relationship.
- bad_user 17y agoDon't forget the Natural Language Toolkit ( http://www.nltk.org/ http://www.nltk.org/ ). Rails is just a web framework. Killer? Yes. All you need for many apps? No. And yes, both Django and numpy are also killer packages ... with Django probably being the inspiration for merging Rails with Merb.
- moe 17y agoPython might not have a single "killer-app", but it has a killer ecosystem, which I learned to value higher. Much of the joy in working with python comes from the "already written" effect. Libraries exist for almost any imaginable task, and it doesn't cease to surprise me how good the average code-quality is. It's extremely rare for me to run into a foul egg, which is a pleasant change from the platforms I've previously worked with.
- 17y ago
- jnoller 17y agoAlso see Michael's post: http://www.voidspace.org.uk/python/weblog/arch_d7_2010_01_02.shtml http://www.voidspace.org.uk/python/weblog/arch_d7_2010_01_02... (http://news.ycombinator.com/item?id=1036400 http://news.ycombinator.com/item?id=1036400)
- d0mine 17y agoDirect link: http://www.voidspace.org.uk/python/weblog/arch_d7_2010_01_02.shtml#e1146 http://www.voidspace.org.uk/python/weblog/arch_d7_2010_01_02...
- swolchok 17y agoI thought Unladen Swallow had good reasons to be on 2.x, such as the fact that Google is on 2.x internally. Maybe Google's decided it's time to migrate? EDIT: the FAQ I was thinking of is at the top of http://code.google.com/p/unladen-swallow/wiki/FAQ http://code.google.com/p/unladen-swallow/wiki/FAQ . They do say 2.x internal, but willing to port to 3.x to get it merged with mainline.
- bioweek 17y agoDoes this mean Unladen Swallow is giving up? Just kind of liquidating the useful things they made into Python proper?
- kingkilr 17y agoGiving up! Quite the opposite, the goal the entire type was for Unladen Swallow to be merged back into Python itself, so everyone can benefit. Bringing it back into CPython gives it the potential for the most eyeballs. I don't know whether Google will continue to pay devs to work on it full time, but certainly the community won't let it languish!
- garnet7 17y agoThis is pretty amazing news. Last I heard, I thought that UnladenSwallow was 2.x-only. Now it turns out that it's going into 3.x and there will be no 2.x Unladen. Wow. Really great news for Py3k.