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.
Thanks for sharing this tip. I am personally not as good at the whole thing so I really appreciate every tip that I get from sites that I have been trying to learn more from.