If you’re like me, you missed PyCon North America 2014 this year. It happened last weekend. While the main conference days are over, the code sprints are still running. Anyway, for those of you who missed PyCon, they have released a bunch of videos on pyvideo! Every year, they seem to get the videos out faster than the last. I think that’s pretty awesome myself. I’m looking forward to watching a few of these so I can see what I missed.

I had heard about the Python Brochure Project last year but was under the impression that it was for corporations at that time as it seemed that you had to purchase them. It looked really good, but since I wasn’t a corporation and couldn’t buy them in bulk, I didn’t give it too much thought. However the Python Software Foundation has now released a preview of the brochure that’s worth a look. The brochure is for the marketing of Python, primarily for non-technical people (such as managers). If you’ve been struggling to get Python adopted at your place of work, this brochure might help as it showcases how Python is used in business in various fields from industry and science to education and government.

You can download it from their website and take a look. I thought it was pretty slick. You can even submit your own case studies to be included or help sponsor the brochure. Go check it out and spread the word!

The website is finally getting a much needed update and at PyCon 2013, they announced that you can now check out a preview of what it’s going to look like here:

There’s a call for beta testers at the bottom of the website, so if you want to help Python, here’s a really simple way for you to do so. They’re still putting content on the site, so it’s going to be kind of rough for a while with placeholders and what-not, but I like the look and feel already. Go check it out for yourself and see what you think!

The Python Software Foundation recently put out an announcement about a central Python events calendar. I thought that was really cool, so I’m reproducing their announcement here. Spread the word!


Central Python Events Calendars

maintained by the Python Software Foundation (PSF)
and a group of volunteers


The PSF has put together a team of volunteers who are maintaining a
central Python events calendar. We currently have two calendars
in place:

* Python Events Calendar – meant for conferences and larger gatherings
focusing on Python or a related technology (in whole or in part)

* Python User Group Calendar – meant for user group events and other
smaller local events

The calendars are displayed on and in a smaller
version in the sidebar of the website (at the moment
only the main events calendar is shown there).


If you want to have entries added to those calendars, please write
to and include the following information:

* Name of the event
* Type of the event (conference, bar camp, user group, etc)
* Focus on Python
* Location and country
* Date and time (if relevant)

For recurring events, please also include a description of the
recurrence in a way that’s compatible and supported by Google


More information on the calendars, the URLs, feed links, IDs, embedding,
etc. is available on the wiki:

Some teens from around the world decided to learn Python using Raspberry Pi to write a game during a sprint starting today and running through tomorrow. They are taking donations to give to the Raspberry Pi foundation too. You can follow their live stream if you want to. Raspberry Pi is an ARM GNU/Linux box for $25. I thought this was a fun project that my readers might find interesting.

I didn’t think I’d do one of these link roundups this week, but I decided to go for it anyway. In fact, I found a cool little tool for obtaining information about installed Python packages and querying packages available on PyPI (Python Package Index) called yolk too! Anyway, here’s this week’s reading list. I hope you enjoy them!

Feel free to drop me a line on your favorite articles this week in the comments below.

It’s the first Friday of June and I’ve read a bunch of new articles this week. From the Vern’s rant about getting Python jobs to a review of the web2py cookbook, there’s lots of fun things going on in Python land. Here are just a few other articles I thought were interesting:

As usual, if you happen to have read something neat about Python this week, feel free to link to it in the comments!

I haven’t done a weekly round-up of Python links because no one seemed to really care when I was doing those. However I thought I’d give it one more try and see if there was any interest this time around. This past week, I finished reading my first web2py cookbook. I’m told there’s another book too, but I haven’t checked it out yet. I suspect had I read the other one first, the cookbook would have made more sense. If you’ve been a regular reader of this site, you’ll notice I’ve done several other book reviews the last couple of weeks too. Speaking of reading, here are just a few of the articles that stuck out to me this week:

I don’t want to overload you on links and I know this one is older, but I have been really interesting in following Katie C’s gaming adventures. So I’ll leave you on that note. I hope you enjoy the articles as much as I did.

I’m a little excited today as my first patch (and first ticket even!) has been accepted. And it really didn’t take very long either. Less than 24 hours after I had submitted my first patch, I got my contribution added. I did have to submit to more variations of the patch though as my first one wasn’t quite right. I wanted to give a shout out to Brian Curtin and Eli Bendersky who helped me figure all this stuff out and made my first foray into core Python development a success. Personally, I think it would have been a success even if the patch wasn’t accepted as I still learned a lot along the way.

Things to take away from the experience:

  • Try to stay on topic! I actually found a second issue with the paragraph I was fixing in the devguide and that probably should have gone in a separate bug report.
  • Number your patches! I don’t know why I didn’t think of that, but Eli told me I should do that in the future to make it less confusing for the committer. That was a face palm moment.

I’ve been reading some of the supposedly “easy bugs” and trying to figure out where else I can help. I already spotted another typo in the docs that are included with Python itself which I’ll probably try to fix. Of course, I want to actually contribute to the code, not just the documentation, but I am probably more likely to be able to find documentation bugs I can help with. Hopefully with more experience I’ll be able to contribute more effectively. Happy hacking my fellow Pythoneers!

As I mentioned in my last article, I figured I’d try to find something that I could patch in Python and submit it. While writing the other article, I stumbled on a minor error in the Python devguide in the Windows section. While it’s nowhere near as cool to patch a piece of documentation as I think it would be to patch Python, I think it’s rather appropriate for me as I tend to contribute more documentation than anything else lately. So I am going to explain the process as I found it. (more…)

Next Page »