Great post - I wish there was a unified resource for things like that for other languages/tools. I would only add iPython - a must for any console adventures.
bpython is much simpler, yet still helpful.
Python Ecosystem - An Introduction
41–50 of 78 posts
Re: Python Ecosystem - An Introduction
#42A formidable effort. It might be matter of taste but recommendations given starting from "Understanding the packages" and to "Install packages that need compiling" are almost harmful. My preference: * you should not care what is your `sys.path` looks like. You need it for debugging if something goes horribly wrong. A tutorial might mention it but things like `sys.path.insert(0,..)` should be avoided or accompanied wi…
Yes, system packages should be managed by a system packager. Unfortunately, for Debian and/or Ubuntu, those packages are often a full version number behind the PyPi version (I'm guessing it's the same for RHL/Fedora). Be very careful using a system packager like apt-get or yum to install a package that is under active development. In that case, it's often better to install from source or use pip/easy_install. But yes, if it's not a system package, don't use sudo for security reasons (although PyPi is pretty safe).
Re: Python Ecosystem - An Introduction
#43would make a good idea for a startup...a Python host that has a simple checkbox interface for installing all this stuff.
That way you can get started with coding instead of having to install everything by yourself.
Re: Python Ecosystem - An Introduction
#44I mostly dabble with python. I learned a little reading this, and it raised some questions for me. Is there a reason --distribute is not the default behavior of virtualenv? Is there a plan to incorporate the stuff virtualenvwrapper does into virtualenv (virtualenvwrapper is a pretty cumbersome name, if for no other reason)?
Re: Python Ecosystem - An Introduction
#45Thank you for this article. As per the Pragmatic Programmer, I thought I would learn Python this year. It's been a tremendously frustrating experience getting a workable stack installed. I wish the famous " One -- and preferably only one -- obvious way to do it " Python design philosophy extended to actually installing everything :(
Just curious - which OS/distribution are you on? Ubuntu and Gentoo (and virtualenv+pip if necessary) both make the Python stack a total no-brainer for me.
Re: Python Ecosystem - An Introduction
#46I think that
$ sudo apt-get install python-pip
is a bad idea.
You should not mix multiple packaging system on your operating system. And more you can dammage it pip provide more recent package than your distro. And if you upgrade a lib that have an incompatibility with a part of the system, you can corrupt it. I have no example to give but I am sure you can find it... Ubuntu now have many tools written in python.
You should use pip inside a virtualenv only. And, fortunatelly when you create a virtualenv, pip is installed in it, and you don't need to use the --distribute to have it.
Re: Python Ecosystem - An Introduction
#47Nice article but you have a typo: updrage instead of upgrade :)
And at the end, it should be "omission" not "ommision". Thanks a lot, wish I had this years ago.
Re: Python Ecosystem - An Introduction
#48Great post - I wish there was a unified resource for things like that for other languages/tools. I would only add iPython - a must for any console adventures.
ipython has known issues running certain code. It is not guaranteed to function like a normal interpreter. If you insist on a fancy interpreter, use bpython.
Re: Python Ecosystem - An Introduction
#49I'd love to have one of these for Ruby. Every time I want to try out something written in Ruby I run head-first in to the packaging problem - Debian and Ubuntu don't appear to like shipping a working gem (presumably because it conflicts with how apt likes to do things) and the documentation on how to resolve the resulting inscrutable error messages isn't particularly easy to find. The Mac is a bit better, but I still…
The gem issue is actually fixed in Debian testing. Not sure when it'll arrive in Ubuntu, but it can't be soon enough.
Re: Python Ecosystem - An Introduction
#50Nice list. I would replace django with web2py, it is closer to the python philosophy imho.