tshepang

10 ms·

61.
Tryton 3.2 release(tryton.org)
2 points by tshepang 12y ago|0 comments
62.
Try Finally Python Quiz(nuitka.net)
1 points by tshepang 12y ago|0 comments
63.
Booting Ubuntu with systemd: Test packages available(piware.de)
1 points by tshepang 12y ago|0 comments
64.
by tshepang 13y ago
"never" is a very strong word: * PyPy has a 3.x branch, which is apparently nearly complete * Major distros, Ubuntu and Fedora, are also moving; Debian is also discussing it
65.
by tshepang 13y ago
You are reading that wrong. Having 3.x support does not imply lacking 2.x support. In fact, I believe all those libraries support both 2.x and 3.x.
66.
Debian/Hurd switches to sysvinit(teythoon.cryptobitch.de)
2 points by tshepang 13y ago|0 comments
67.
by tshepang 13y ago
1.13, released on 2014-03-14, does support Python 3. It's just someone must have forgotten to update PyPI metadata to indicate so.
68.
by tshepang 13y ago
It's just bundled, meaning it's still developed externally. In fact, 3.4.1 will include a newer pip version.
69.
by tshepang 13y ago
My favorite quote (from a comment): "Aaarrrrrgggghhh. Markdown sucks the anus of a syphilitic camel."
70.
by tshepang 13y ago
I would rather they be made easier to enable (currently one has to edit an .INI file). That would be better than trying to appease some hypothetical from-Git converts.
71.
by tshepang 13y ago
I created this list to help me stop worrying: http://tshepang.net/major-projects-using-mercurial .
72.
Debian: developing it wrong(blog.liw.fi)
2 points by tshepang 13y ago|0 comments
73.
Nice paramiko tutorial (2009)(jessenoller.com)
1 points by tshepang 13y ago|0 comments
74.
If You Like Your Init System You Can Keep It(braincells.com)
3 points by tshepang 13y ago|0 comments
75.
Book review: Introduction to Computer Science Using Python(neopythonic.blogspot.com)
1 points by tshepang 13y ago|0 comments
76.
The stupidest trend in laptop design(ramblingfoo.blogspot.com)
31 points by tshepang 13y ago|65 comments
77.
A (libre software) vision wanted(enricozini.org)
2 points by tshepang 13y ago|0 comments
78.
C++, it's time to go(blog.irukado.org)
23 points by tshepang 13y ago|31 comments
79.
by tshepang 13y ago
When 2.7 stops getting bug/security fixes? Current plan is 2015: http://www.python.org/dev/peps/pep-0373 .
80.
by tshepang 13y ago
If this is not a joke, Zed is paranoid.
81.
by tshepang 13y ago
If 'raises questions about governance' means the leadership can't predict the future, then I agree. Else, this is not fair, since features were added to Python 2.6 to reduce migration pain (which incidentally enabled this sin
82.
How to support both Python 2 and 3(ondrejcertik.blogspot.com)
84 points by tshepang 13y ago|22 comments
83.
by tshepang 13y ago
What are you referring to by 'new platform'? ARM?
84.
Migration Plan to Warehouse, a re-implementation of PyPI(mail.python.org)
1 points by tshepang 13y ago|0 comments
85.
Using Pelican with Heroku(blog.getpelican.com)
1 points by tshepang 13y ago|1 comments
86.
Roadmap for fixing Python packaging(mail.python.org)
1 points by tshepang 13y ago|0 comments
87.
The future of Gittip(medium.com)
1 points by tshepang 13y ago|0 comments
88.
Impressive Libreoffice clean-up work(people.gnome.org)
2 points by tshepang 13y ago|0 comments
89.
Open Products(thechangelog.com)
1 points by tshepang 13y ago|0 comments
90.
On Teaching Programming With Python 3.0 (2008)(comp.leeds.ac.uk)
3 points by tshepang 13y ago|0 comments

More ›