namedtuple, classes and dictionaries are no longer the only options to represent a key/value mapping where all they keys are known upfront: Records may be a better alternative and they’re now available in Python via PyRecord.
This late issue of The Software Practitioner’s Digest, the first in 2012, highlights resources published in January in Better Software, Dr. Dobb’s, IEEE Software and Software Engineering Radio.
This digest has been the most difficult to compile so far, given how hesitant I was with regards to the inclusion of some research articles and essays which — although very revealing or thought-provoking — did not have much (or any) actionable material for practitioners. I decided not to include them in this issue, but I’d like to know whether my modest readership would enjoy finding articles that are simply interesting in future issues (rest assured that these would be backed by some evidence!). Please let me know what you think!
This is the third issue of the The Software Practitioner’s Digest, covering the little activity from December 2011 — A very quiet month not only because of the holiday season, but also because it’s an even month and the periodicals I follow are published in odd months. The next issue should be along the lines of the October and November issues, so stay tuned!
I’ve just uploaded the materials for my tutorial at EuroPython 2010, “WSGI from Start to Finish”. You can also get the slides and the WSGI cheat-sheet individually. I’ve updated the slides so that they make sense even without me speaking; so now they have references to the code examples.
The tutorial was recorded and should be published on the EuroPython Web site after the event.
This was the first time I give such a long talk. Three hours talking about WSGI! But it was really fun. And the room was absolutely full, which I couldn’t believe.
This article first appeared in the May 2009 issue of Python Magazine and has been slightly updated. The contents of the article are only applicable to repoze.who 1.0 and repoze.what 1.0, not repoze.who 2 and repoze.what 1.1 which are under development as of this writing.
Have you ever created a Web application? If so, it’s very likely that you have at one time or another faced “the security problem”; whether to create and maintain a homegrown security sub-system, or to learn to use framework-specific security mechanisms (which may not be as flexible as you wish).
Securing Web applications shouldn’t be a problem. This article explores a highly extensible alternative which you can learn once and use in arbitrary applications, regardless of the Web framework used (if any!).