Python (Flask, Fabric, Jinja) and Amazon EC2. A nice walk through with code for contribution and reuse.
Python packaging options are so varied, so strongly disputed as to what is ‘best’ or ‘correct’ or ‘the past’ that they are as un-Pythonic as can be. I love Python, but when it comes to packaging, well lets say I understand how Armin Ronacher feels.
- Python Ecosystem – An introduction – mirnazim.org
- How I learned to stop worrying & love Python Packaging – Jannis Leidel – Slideshare
- Building and Distributing Packages with setuptools – PEAK
- Taming your dependencies with pip – Carl J Meyer – github
- What is softwares in Python which are alternative to Ruby’s bundler / Perl’s carton? – Stack Overflow
- The Hitchiker’s Guide to Packaging
- Why use pip over easy_install? – Stack Overflow
- Python Packaging: Hate, hate, hate everywhere – Armin Ronacher
- Poster on the future of Python packaging for PyCon US 2012
- Python Deployment Anti-Patterns
- Tools of the Modern Python Hacker: Virtualenv, Fabric and Pip
One tip: Never, ever, ever use easy_install (except to install virtualenv and pip). If you are going to install or define an .egg, do so with setuptools or distribute. Again: Don’t use easy_install.
Greg Laden recently posted some thoughts about “Python for Kids”, a book by Jason Briggs. Recently I discovered the turtle module, which is heavily used in the book, is included in the standard Python distribution when I tripped upon a tutorial at the Open Book Project. I’m going to have to buy the book and give it a try with Emma.
Tim Bray posted a thought provoker in “Type-System Criteria”. Working in Android has caused him to rethink some positions. Go read.
Greg Wilson discusses one of the biggest road blocks to using Python more widely, especially in teaching situations, in “It Just Keeps On Hurting”.
Here is some great Python related news: Adrian Holovaty is getting back involved with Django!.
Alex Clemesha wrote a blog post back in 2009 that points to 3 elements of the Python ecosystem that I’ve made part of my toolbox that if you haven’t read, is worth a read: “Tools of the Modern Python Hacker: Virtualenv, Fabric and Pip”. I’m pretty sure that without these 3 (and Jenkins/Hudson), recent projects of mine would have been far more complicated to accomplish with teams that have been variable in size from day to day. They reduce complexity, and like Maven on the Java side, I wouldn’t want to do a project in Python without them now.