Live data from Hacker News

Python and Django on Heroku

blog.heroku.com

41–50 of 75 posts

Re: Python and Django on Heroku

#41

Earlier quoted context omitted.

Definitely this. A database is a requirement for a Django app, but not for Flask. I always seem to go back and forth about whether to start a micro-framework like Flask and use plugins and Python libs to assembly a framework that has only what I need, or use Django and (possible) include a lot of code that will never get run.

It really depends on your vision for the app. If this is a single weekend project or a toy web site that you'll likely never touch again, or if you do will only be for minor updates, then I say go for Flask. It'll get in your way less and let you just launch it sooner. For anything larger than that though, Flask has always turned into a giant headache for me. As soon as I ever start to try and organize the project be…

I've been running multi file apps since before 0.7. If you read the documentation or searched mailing lists or looked at example applications you can see how. Blueprints made it even better.

2. In the documentation you will find that you can list out routes just like django. http://flask.pocoo.org/docs/api/#flask.Flask.add_url_rule

Re: Python and Django on Heroku

#42
post #5

Interesting... I wonder if this makes Google App Engine more appropriate for internal apps for Google Apps customers? For quick/easy personal hacking/development having a Python stack on Heroku seems pretty attractive now.

Also, to get something up quick and dirty with a vps or shared host, is fairly easy, I'll agree with you. However, as you need to get more power, it becomes more problematic. With Heroku, the "quick and dirty" way is actually quite robust and can scale well.

But I'm with you that I find it a bit too costly as I know (and actually like) configuring my stuff.

Re: Python and Django on Heroku

#43
post #27

As much as I've come to enjoy and appreciate the various start-ups whose mantra was "We're Heroku with Python/Django capabilities", it will be interesting to see which of those survive the next 8-12 months now that Heroku officially supports that stack. It'd be a shame to see ep.io and Gondor go the way of the dodo bird, but what sets them apart now?

Heroku is owned by Salesforce now and subject to their agenda. Could be a good thing for some reasons, but it leaves room for a nimble startup to use the start-up advantage (fast moving, close to customers, unencumbered by a corporate leash) to compete. They're going to have to keep moving though.

A year ago I would have agreed with you, but Heroku has been on a roll lately introducing features at a very fast pace. The party may end eventually, but I've been really pleasantly surprised by their post-acquisition actions so far.

Re: Python and Django on Heroku

#44

As much as I've come to enjoy and appreciate the various start-ups whose mantra was "We're Heroku with Python/Django capabilities", it will be interesting to see which of those survive the next 8-12 months now that Heroku officially supports that stack. It'd be a shame to see ep.io and Gondor go the way of the dodo bird, but what sets them apart now?

Epio cofounder here - we're not worried by this, and we've known it was coming for ages now.

The hosting market is plenty big enough for more than one player - we're expanding to multiple languages, much like Heroku expanded from Ruby, which provides an ample feeding ground of old-style hosts to slowly steal business from - and there's also still a lot of room for innovation.

Heroku, as much as I like their product - and I do, which is why we started this a year ago - still has its flaws and idiosyncracies, some of which are those low-level-design type of choices where if you go the other route, a different set of people complain. You can't be all things to all people, and I don't think anyone will end up being that.

Re: Python and Django on Heroku

#45
post #39

Python 2.7? They’re years ahead of Google App Engine! Addendum: The previous statement is slightly tongue-in-cheek, but: (1) GAE is running a version of Python (2.5) so old, that it’s hard to get fully patched binaries of it anymore (depending on your platform); and (2) By “years ahead,” I don’t mean it will take Google years to catch up, but merely that their Python version is years old. Puzzling, given that Guido w…

App Engine announced they will release a Python 2.7 runtime in several months. It's currently in their trusted tester program.

Re: Python and Django on Heroku

#46
post #19

This is great! Looking at the Django tutorial in the docs [1], I think it's too bad, though, that they don't provide a build-in, well tuned WSGI Server. This way, you have to choose your own WSGI server, configure and update it yourself. [1] http://devcenter.heroku.com/articles/django#using_a_differen...

We do not automatically use a wsgi server because we want to offer flexibility to our users. Additionally we felt that having less magic in what we automatically do to your application (other than run it) was more of the Python way.

> "was more of the Python way."

That you tailor each environment to the language/framework around it is a great touch.

Re: Python and Django on Heroku

#48
post #45
post #39

Python 2.7? They’re years ahead of Google App Engine! Addendum: The previous statement is slightly tongue-in-cheek, but: (1) GAE is running a version of Python (2.5) so old, that it’s hard to get fully patched binaries of it anymore (depending on your platform); and (2) By “years ahead,” I don’t mean it will take Google years to catch up, but merely that their Python version is years old. Puzzling, given that Guido w…

App Engine announced they will release a Python 2.7 runtime in several months. It's currently in their trusted tester program.

More details on 2.7 and GAE: https://sites.google.com/site/gaepython27testing/

Re: Python and Django on Heroku

#49

Earlier quoted context omitted.

It really depends on your vision for the app. If this is a single weekend project or a toy web site that you'll likely never touch again, or if you do will only be for minor updates, then I say go for Flask. It'll get in your way less and let you just launch it sooner. For anything larger than that though, Flask has always turned into a giant headache for me. As soon as I ever start to try and organize the project be…

I've been running multi file apps since before 0.7. If you read the documentation or searched mailing lists or looked at example applications you can see how. Blueprints made it even better. 2. In the documentation you will find that you can list out routes just like django. http://flask.pocoo.org/docs/api/#flask.Flask.add_url_rule

I've read through all the documentation, and researched extensively. I still ran into problems way too often to ever warrant using it over a full framework for larger projects.

Re: Python and Django on Heroku

#50
Python minimizes magic and maintains backwards-compatibility? LOL.

(I'm a programmer who recent dived into python - it's awesome and it's easily my favourite language to use now - but those statements are fallacies).

Post reply on HN