You’re like “Change Python’s frameworks so they follow Rails” because you seem to like the language and the speed and stuff like that.

Regardless of the initial disclaimer, you’re very biased towards Python (which is fine, I’m just pointing it out).

I personally have a strong distaste for any language which imbibes white space with meaning. It strikes me as ugly when I use it. But, hey, I’m a smalltalker at heart, and Ruby is way more smalltalkish than Python.

This aside, the real reason I’m posting is to help you out…

You’re missing the main point of why Rails is so successful. It’s the same reason that Apple, Dyson or even Nintendo are so successful.

We, as REAL creators, spend far less time looking around at the competition, and spend time work on creating something that we feel and think is a beautiful thing. There can be no competition for this, because it’s inappropriate to compare.

If you’re not following your own heart – if you’re following someone else’s lead, then you can’t help but not know where you’re going. You’re being led by others, then people are not going to become truly enpassioned about your product, however many bells and whistles there are on it.

The reason the Python community has no “Rails” at the moment is that no one has yet created something that they truly love to use and that is a simple, elegant solution for Web Development.

The reason all of these aforementioned communities have such enpassioned userbases is that they love the things. They’re literally created out of love, and so they have love in them. They’re therefore lovely to use.

- Random8r

It’s nice that in Java every string is Unicode. Or rather, Unicode 3.0. If you want to support anything outside of the BMP, you practically have to implement half of UTF-16 decoding yourself. You need 2 “char”s to represent some Unicode code points — not fun.

Python is much nicer, because you get any Unicode character (all 21 bits) in a string. There’s also a str (ASCII) type, but you can simply skip it for now. (In Python 3, this will be fixed.)

I’d summarize the difference as “In Java, you get Unicode 3 for free, and it’s a lot of work to support Unicode 5″ versus “In Python, you get ASCII for free, and it’s little-or-no work to support Unicode 5″.

On the top, though, are Lisp implementations like SBCL, which combine the best features of Java (every character and string is Unicode-capable) and Python (full 21-bit characters for free). This isn’t surprising: Lisp predates ASCII.

I’ve not done any Unicode work in Tcl or Ruby yet, so I can’t speak to those.

Another Python ORM for you to play with from the guys that brought us Ubuntu, Canonical.

https://storm.canonical.com/

Clean and lightweight API offers a short learning curve and long-term maintainability providing the following features:

o Storm lets you efficiently access and update large datasets by allowing you to formulate complex queries spanning multiple tables using Python.
o Storm allows you to fallback to SQL if needed (or if you just prefer), allowing you to mix “old school” code and ORM code.
o Storm handles composed primary keys with ease (no need for surrogate keys).
o Storm handles relationships between objects even before they were added to a database.
o Storm works well with existing database schemas.
o …and more.

“Use the routing systems of Pylons and Django.”
the Routes are much better solution than Django’s URLs. Specially for maintaining existing urls. In Django you have to hardcode URLs in templates or controllers.

“Get the publicity machine going.”
I think this point is crucial, especially in Pylons case. Marketing is very important – don’t underestimate.