These are my notes from the Design Summit and Conference kicking off the Folsom release of OpenStack, held April 16-20, 2012 in San Francisco, CA. Much more happened than I could hope to capture in a single post, but I can publish most of my notes from the design sessions.
What’s New in 3.2 Make project_dir a local variable so that cdproject does not interfere with other variables the user might have set. (contributed by slackorama) Fix typo in documentation reported by Nick Martin. Change trove classifier for license “MIT” to reflect the license text presented in the documentation. This does not indicate a change in the license, just a correction to the expression of that intent. (contributed by ralphbean as fix for issue 134) Extend rmvirtualenv to allow removing more than one environment at a time.
What’s New in 3.1 Fix a problem with activation hooks when associating a new virtualenv with an existing project directory. Fix a problem with add2virtualenv and paths containing “special” characters such as &.
I joined DreamHost about four weeks ago on Feb 6. and am on the team building a cloud hosting service based on the open source project OpenStack. I spent the first couple of weeks at the new job doing the usual sorts of new-hire activities: reading a lot of documentation and learning my way around the development environment and tool chain. I’ve done a little bit of work on some internal code already, and I recently had a good opportunity to start working on OpenStack itself.
What’s New? Use docutils as a library instead of shelling out. Switch from BeautifulSoup to pyquery. Add tags directive to specify the tags or categories for a new post.
When you’re writing code to search a database, you can’t rely on all those data entries being spelled correctly. Doug Hellmann, developer at DreamHost and author of The Python Standard Library By Example, reviews available options for searching databases by the sound of the target’s name, rather than relying on the entry’s accuracy.
Searching for a person’s name in a database is a unique challenge. Depending on the source and age of the data, you may not be able to count on the spelling of the name being correct, or even the same name being spelled the same way when it appears more than once.