I umpire college baseball and have looked into mounting a GoPro on my mask for a game, and may do it, but won't be able to do it during the regular season. Could still be fun to show in a summer league where it's slightly more relaxed but still competitive baseball.
Having seen the view of a few other GoPro mask cameras lately, it's pretty cool to see pitches coming in, but commentary is the best part. The chatter was my favorite part of that AHL video by far, but perhaps I'm biased also being an official.
I don't know where you got this, but it was never planned to have been dead two years ago. 2.7.0 happened in July 2010, and regular bug and security fixing would still have been happening up until around this time regardless of anything else (fwiw, 2.6 went from 2008-2013). Instead, we decided earlier this year to extend that support until 2020.
> If Python 3 is so wonderful, why are the Python 3 developers still using Python 2 in their toolchain? It's because it would reportedly take 1 man year to port Mercurial to Python 3.
Why would that have anything to do with it? We didn't write it and don't have any input into Mercurial, and it works fine for what it's used for right now. It's a source control tool, not a library we use in any way.
If we did the subversion switch today, it'd be to git, which again has nothing to do with Python versions (obviously).
For my PyCon Russia talk, I pulled down the data for all 44,402 packages (as of May 31). 13.5% of all packages on PyPI support some version of Python 3. 75.5% of the top 200 packages by download count claim to support some Python 3 version (according to their setup.py classifiers). Additionally, 64% of the top 500 support some Python 3 version.
Another interesting thing I saw was that of those 44K packages, 44% of them have seen a release within the last 12 months (representing 82% of the last month's download share), and 22% of those packages released in the last year support some version of Python 3.
> In the past, RubyGems was hosted on dedicated hardware within Rackspace. While this was certainly cheaper, it created administrative issues. Granted those can be solved without using AWS, but we get back to again desiring to have as low of friction on the administration as possible.
If Rackspace can be of assistance in the future, feel free to reach out (firstname.lastname@example.org). We currently donate hosting to many open source projects, including ones in a similar space, like the Python Package Index.
Note that if you can get Rackspace or whomever to donate the hardware/bandwidth, you can use less than 7k/month to hire a very competent admin to solve the administrative issues, which would probably lead to better service for everybody.
Yep, I wasn't able to get to everything. I had to update a ton of the content via the Django admin without a source checkout (which is now available), so I couldn't grep for placeholder text. We'll get it all straightened out.