jnoller

42 ms·

421.
A Fireside Chat with Guido van Rossum(us.pycon.org)
2 points by jnoller 16y ago|0 comments
422.
Introduction to Distributed Filesystems(pl.atyp.us)
4 points by jnoller 16y ago|0 comments
423.
by jnoller 16y ago
Actually, Python generators will be changing quite a bit soon: http://www.python.org/dev/peps/pep-0380/
424.
by jnoller 16y ago
No Big plans on threading: Developer and Patch needed. Functional programming: No one has proposed it, Developer and Patch needed. There's a trend here - developers propose things for inclusion and changes to python based on needs, availabi
425.
by jnoller 16y ago
Since you took the time to write such a big reply - I owe you the same courtesy. First: I'm not referring to you as a naysayer, just trying to clarify the timeline (both expected and perceived). No - your comments were far from the single c
426.
by jnoller 16y ago
What sort of ambitious things?
427.
by jnoller 16y ago
Brett and I were just discussing this - and he put up a post summing it up nicely: http://sayspy.blogspot.com/2011/01/my-semi-regular-reminder-... Short version? We planned on it taking at least 5 years. Armin's point is that Python 3 i
428.
by jnoller 16y ago
See also: http://news.ycombinator.com/item?id=2131214
429.
My semi-regular reminder that Python 3 is on schedule(sayspy.blogspot.com)
56 points by jnoller 16y ago|5 comments
430.
by jnoller 16y ago
We have had answers for the past two years: Python 3 adoption will be measured in terms of years and will only come as third party modules (such as Numpy, Scipy, and many others) slowly make the port. No one has ever claimed it to be publ
431.
by jnoller 16y ago
Brian is completely correct. The problem with DiP3 is that it was one of the earliest adopters. We knew that python 3 would take years (like, 3+) for widespread adoption. Things are going according to plan.
432.
by jnoller 16y ago
See above!
433.
by jnoller 16y ago
I can answer any questions anyone has about this: we've done a lot of work this year to make pycon even more attractive to startups, sponsors and entrepreneurs, and this is one big piece.
434.
by jnoller 16y ago
I have to concur: that's the one bit I disliked about the post. PyCon has always been very, very welcoming and friendly to me and many others.
435.
by jnoller 16y ago
It's less that they don't "know" python - but rather that they only know a little. I know when I attended my first pycon, while I had been using Python a bunch I could have stood to spend some quality time in Zed's class, and generally suck
436.
by jnoller 16y ago
Echoing the sentiment this is a fantastic idea. Count me in for helping out too as needed.
437.
Learn Python the Hard way Class At PyCon 2011(sheddingbikes.com)
34 points by jnoller 16y ago|14 comments
438.
Basic Wysiwym Markdown Editor: jquery-wysiwym(pushingkarma.com)
2 points by jnoller 16y ago|0 comments
439.
by jnoller 16y ago
Storing data in the cloud can and should be safe though, the ideas of economy of scale, and secure storage should not be mutually exclusive.
440.
by jnoller 16y ago
It's important to note that the Nasuni product (I am employee) makes cloud storage behave very much like local storage. We're not a "cloud storage" company so much as a gateway to enable companies to securely use cloud storage and have it b
441.
Cloud Storage Isn’t Cheap: Price of the Cloud Compared to Traditional Storage(nasuni.com)
17 points by jnoller 16y ago|14 comments
442.
All PyCon 2011 talks and tutorials announced(us.pycon.org)
40 points by jnoller 16y ago|6 comments
443.
PSF Sponsored Sprints - now more than just CPython(pythonsprints.com)
2 points by jnoller 16y ago|0 comments
444.
by jnoller 16y ago
And you're right; final approval won't come because well, it ain't done.
445.
by jnoller 16y ago
Part of the reason Python 2.7 is faster on some benchmarks is because of the patches the unladen swallow team pushed upstream into core.
446.
by jnoller 16y ago
If this is a flame war, then it's a pretty tame one :) As for Google's intentions, I've learned (as it has been explained to me time and time again) - never attribute smaller decisions to a larger strategy or "plan" of Google's. It probably
447.
by jnoller 16y ago
Look at the header - 3.3 the intention was to accept the PEP, do the merge, and then ask for final approval for merge into Py3k. The intention on both sides was to always merge it into vanilla Py3k.
448.
by jnoller 16y ago
When asked - on the mailing list, on google buzz, or anywhere else, Collin and Jeffery and others have been very open about its status. They've always dealt us (as the community) a fair hand about the status of the project, and the path mov
449.
by jnoller 16y ago
No one was using Unladen Swallow jacquesm - it was an experimental fork of CPython.
450.
by jnoller 16y ago
No, it's not dead, and I'm sad that this is sitting at the front page, because it's so misleading. The fact is, it's stalled ( https://www.google.com/buzz/bcannon/bZDN1jNZ3uC/Is-this-fina... ) - http://www.python.org/dev/peps/pep-3146/ wa

More ›