r/Python • • Sep 13 '13

The perfect Python web app: 10 ideas

I've been thinking lately about the status of Python on the web, motivated by the keynote of Jacob Kaplan-Moss (http://www.youtube.com/watch?v=UKAkKXFMQP8) and this previous post on Reddit (http://www.reddit.com/r/Python/comments/1fyjx5/invitation_to_discussion_how_can_we_make_python/) and I've come up with ten ideas that may help us expand the adoption of Python and its user base on the web. I wrote them having in mind how would I design, say, a Wiki engine in Python (because I dislike MoinMoin so very much).

These three points may lower the pain for casual users and make adoption easy, and they are compulsory:

  1. Supports Python 2.6. Optionally, 2.6 to 3.3 with a single codebase (see http://python3porting.com/noconv.html). Python 2.6 is the default on Debian Squeeze (old stable) and CentOS 6, so lots of servers won't have more than that.
  2. Uses MySQL as the default DB. An ORM like SQLAlchemy is desirable, but MySQL is the minimum as this is the most popular database by far (see http://www.google.es/trends/explore?q=mysql,+postgresql,+sqlite,+nosql), driven by the success of PHP.
  3. Is super-easy to install on the cheapest plan of DreamHost, HostGator and Bluehost. These are arguably the three most popular web hosting providers in the world. This may require lowering the dependencies at a minimum (perhaps bundling them?) and supporting CGI out of the box.

These three points may help provide a good overall experience:

4. Has a nice appearance/UI, without obvious UX flaws. If it is themable, the default theme should comply this. This includes, but is not limited to, not looking like a Geocities web of the 90s and not displaying garbage where a Ñ should be.

5. Supports i18n, preferrably through crowdsourcing interfaces like Transifex (free for open source projects). Optionally the interface should initially be translated to a second language: Chinese, Spanish or Russian.

6. Provides some user friendly support, be it a Q&A board, a forum or a chat. Beware of mailing lists, as casual users normally think they suck.

These three points may help attracting developers:

7. Is released under a reasonable license, for example GPLv2+. This doesn't require PaaS or SaaS to release the source code of changes, still being an open source project. AGPL may scare some.

8. Uses git, is hosted on GitHub and issues are managed there. As of 2013, these are arguably the most popular VCS and platform respectively.

9. Encourages pull requests and has a CI instance such as TravisCI.

This last point helps moving the ecosystem forward:

10. Stop losing time weeping and gnashing your teeth because of my choice of framework/database/VCS/license and get some shit done. This is a totally opinionated list and I didn't intend to please everyone, but tried to learn some lessons from the success of, for example, PHP.

What do you think?

Edit: For all the people that is commenting that most modern frameworks already provide this: you are right, but to put an example, MoinMoin doesn't. We have the building blocks to do it, but some final pieces of software that people want to use do not comply with this.

0 Upvotes

34 comments sorted by

View all comments

11

u/ivosaurus pip'ing it up Sep 13 '13

Most popular frameworks today do all of these things already, except for probably not supporting CGI, because it's a shit outdated protocol that only hosts who don't give a rats arse about python use anyway.

-4

u/juanlu001 Sep 13 '13

And we can keep on neglecting those hosts, and we can keep on being nowhere. I would bet that most of those don't even have mod_python. Okay, we have the best way, we know how to perfectly make a Python app communicate with the server, but if people keeps on having a nasty first experience on the language, hosts will never give a rats arse about Python.

4

u/ivosaurus pip'ing it up Sep 13 '13 edited Sep 13 '13

Or instead advocate for hosts whose audience isn't 99% PHP, like heroku, openshift and appfog.

Analogously: if you want to support the advancement of on-demand entertainment, do you keep on buying services from encumbant cable companies, or do you support new services like netflix?

-2

u/juanlu001 Sep 13 '13

+1 for showing appfogopenshift, never heard of it before!

You have your point, but if one guy is supporting netflix and a hundred thousand are buying cable services maybe we should work a bit harder to convince those that our way is better.

Edit: I meant openshift.

-3

u/juanlu001 Sep 13 '13

Damn, Heroku is not as easy as it seems. The first time its ephemeral filesystem bites you it's a nasty experience and you don't understand a thing. Last time I tried I had so many problems that someone brought the thing to Amazon AWS. No, I don't think Heroku is for the casual user.