Previous threads about learning Python vs Ruby:
http://news.ycombinator.com/item?id=741257
http://news.ycombinator.com/item?id=682101
http://news.ycombinator.com/item?id=1258099
http://news.ycombinator.com/item?id=1078628
Also, you're comparing a framework and a language, a better comparison would be python with ruby or django with rails...
I know it's a bad comparison, but that seems to be what most people pick from...since ruby almost always is picked with RoR
Knowing what I know today, I would probably try my luck with Python, as I've too often been bitten by Ruby's lack of properly documented, stable libraries. However, I think I would miss the power of Ruby's easy metaprogramming facilities. Clojure comes to mind as a third option...
o_O, example?
I've often turned to Ruby due to it's awesome documentation and actively developed gems.
You can compare Ruby with Python, or Rails with Django.
There are quite a few web frameworks for Ruby now as well (Sinatra -> Padrino, Merb, Nitro, Waves) ..
I think it's useful to know both languages. And pick whichever framework fits the problem domain best. Django is obviously really good for publishing. Rails is great for B2C. If you intend to market a SaaS API to businesses, and you expect lots of traffic, maybe even a framework in another language will be a better fit.
Ruby and Python are more alike than any other pair of languages I know. The frameworks however, can be quite contrasting.
I've pretty much stopped using package managers tho. Sometimes I may use pip to install some library, but most of the time, I try to keep everything (full packages) cached in a "lib" subdirectory and install on-demand. Even for Flask extensions, I try to to manually copy the libraries to lib/flaskext instead of letting pip handle it for me. The benefits of this is that you're never dependent on ANY package manager to run your app, and you keep all your dependencies frozen in your project's repository. (PS.: I f_cking hate git submodules).
The other thing I've been doing is using a more Unix-y configuration style (https://gist.github.com/aa9158d559c642fed619). My Python web applications today consist of an app.py file, an app.conf file, a support.py file (which loads all dependencies isolatedly and then I just do "from support import *" in app.py), a lib/ directory with dependencies and fabfile.py. In fabfile.py, I usually have a "web" task to start the development server and many other small tasks I add as I go. It can't get any simpler than that.
I have played with Python only lightly, but that I did play with seemed to talk a lot about Ruby libraries recoded for Python. I stopped what I was doing and went back to Ruby as I felt there was no point in working with doppleganger libraries rather than the original. Why work with something that often aspires to be it's competitor.
Both have a good following. From my experiences I will always stick with Ruby. I see it happen countless times again. Most of my designer friends go with Python and most of my programmer friends go with Ruby. Honestly, both are good languages all the same.
Try them both out briefly and see which you prefer?
Unless you ask just the people who looked at Ruby and Python at the same time, I think your poll will be weighed to whether readers were Python devs first or Ruby devs first.
I find Ruby's syntax a bit "magical" and that it makes groking RoR a bit hard once you go beyond the basics. I would recommend Python over Ruby for a Java/PHP/C# expat willing to learn something different.
That said, my latest new language has been Clojure.
Python on Zope would be my choice. It kicks RoR ass since 1999.
Python on Dope sounds fierce. Snakes and drugs are cooler than jewels and trains.
So that's like saying "Yep, I can confirm that Python and Ruby are indeed programming languages."