I am not sure why Requests gets this much press. httplib2 has all the features of Requests and more, and their APIs are not that different.
Python Ecosystem - An Introduction
61–70 of 78 posts
Re: Python Ecosystem - An Introduction
#62great post!
Re: Python Ecosystem - An Introduction
#63A 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…
> System packages should be managed by a system packager.
You shouldn't be using the system Python. Should compile from source and put in /opt//. And that shouldn't be owned by some random user. So, you should be using sudo.
Re: Python Ecosystem - An Introduction
#64would 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.
http://enthought.com/products/epd.php (Disclaimer - I work for enthought)
Re: Python Ecosystem - An Introduction
#65NOTE: there's brokenness lurking in urllib and email modules. The python library modules are more often than not modeled on perfect reality rather than a pragmatic one (e.g., complete violations of RFCs). BTW, if one reads re.py in the dist, you'll notice that it hasn't been touched by Fredrik Lundh since 2001!
I should say I still love python. Its the most fun I've had programming next to Scheme, and well, NodeJS is kind of fun too (in an algol way).
Re: Python Ecosystem - An Introduction
#66Thank you, thank you, thank you. I've been looking for something like this for ages. While Python the language is fantastic, I have found getting into the whole environment quite tricky so your guide is fantastic.
Re: Python Ecosystem - An Introduction
#67Earlier quoted context omitted.
My indented audience was not the pure beginners. I was targeting for developers coming to python from other platforms. Over past 2 years, if I have learned one thing while training interns, trainees and experience devs in Python/Django, it is that packaging confuses people a lot. apt-get vs easy_install vs pip. That is why I choose to spend most time on package management and virtualenv etc. I think, I should have in…
Great Pythonesque pun there! indented==intended, I'm sure.
This happens to me all the time. My most favorite is when I have to type the word "important", my mind spells "I M P O R T A N T" but my fingers instinctively stop at "import".
Re: Python Ecosystem - An Introduction
#68In the section of "The Development Environment" you should mention the buildout (http://www.buildout.org/). It is a very simple way to reproduce an enviroment.
Re: Python Ecosystem - An Introduction
#69I 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…
What I tell people is that Python (as installed by apt-get, yum) is not on your system for you to develop with. It is there because some of the system tools are written in Python, including at least part of the apt packaging system. It's also there for System admins to use for writing Python scripts instead of bash scripts. But for app development, get your own Python, manage it yourself and install 'distribute' so t…
I don't anderstand why you want to use the --distribute to have pip and easy_install installed.
If you do not, you also have those tools.
Re: Python Ecosystem - An Introduction
#70Great 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.
Definitely; IPython is great at making Python more self-documenting, with completion, the ? help function, and the ability to embed an interpreter anywhere in your program.