As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I would like to know your opinion of which of these two web frameworks (Django & webapp2) is better for using on App Engine Platform, and why?
Please don't say that both are completely different, because Django is much more complete. Both are the "web frameworks" you can use in App Engine.
Choosing between Django and webapp2 really depends on what you're using it for. In your question you haven't given any of the parameters for your decision making, so it's impossible to tell which is "better". Describing them both as "web frameworks" shows you haven't done much research into what they are.
Webapp2 is essentially a request handler. It directs HTTP requests to handlers that you write. It's also very small.
Django has a request handler. It also has a template engine. It also has a forms processor. It also has an ORM, which you may choose to use, or not. Note that you can use the ORM on CloudSQL, but you'll need to use Django-nonrel if you want to use the ORM on the HRD. It also has a library of plugins that you can use, but they'll only work if you're using the Django ORM. It also has bunch of 3rd party libraries, which will also require the Django ORM.
If you have portability in mind the Django ORM would help a lot.
You'll have to make your decision comparing what you actually need.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am interested in learning more about node.js and utilizing it in a new project. The problem I am having is envisioning where I could enhance my web stack with it and what role it would play. All I have really done with it is followed a tutorial or two where you make something like a todo app in all JS. That is all fine and dandy but where do I leverage this is in a more complex web architecture.
so here is an example of how I plan on setting up my application
web server for serving views:
Python (flask/werkzeug)
Jinja
nginx
html/css/js
API sever:
Python (flask/werkzeug)
SQLAlchemy (ORM)
nginx
supervisor + gunicorn
DB Server
Postgres
So is there any part of this stack that could be replaced or enhanced by introducing nodeJS I would assume it would be best used on the API server but not exactly sure how.
It would replace Python (flask/werkzeug) in both your view server and your API server.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Question is for programmers who have used Django and Flask for real projects.
What challenges do you face going to the Flask?
Interested in the situation when there may be unexpected difficulties (after using django).
Specific examples are welcome.
I tend to use Django for "big" projects and Flask for projects requiring less than a ~300 lines file.
The challenges in moving to Flask are in my sense to go look for the extensions for forms, mails, databases... When you need them, and referring to different documentations. But it is naturally the price of flexibility.
One of the key issue I have been facing was deployment with Fabric. I was used to deploy very quickly with django-fab-deploy and it tooks me a little bit of time to set up a comparable generic deployment solution for Flask.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
i use python+django for my web projects and i love it for code readability and speed development. But now i want something very fast, low cost for resources and simple (minimalism) but in the same time code-readable as django.
Which DB backend to use?
Simple and fast ORM in django style?
Fast template system (with inheritanse)?
Web server written in python (i look at tornado or pyev for async server)?
cache system?
what do you recommend in this case?
Django will suit your purposes. (Unless you're doing high-frequency trading on the stock exchange).
I'd recommend looking into Flask (http://flask.pocoo.org/):
Take your pick
SqlAlchemy
Jinja2
http://flask.pocoo.org/docs/deploying/ and http://flask.pocoo.org/docs/deploying/others/
Not sure
I personally tend to like Tornado a lot lately indeed.
Now, the question is: what are you looking for in a web framework? Fast development? Fast performance? Simple API? Active open source community?
Do you need a full stack framework like django or maybe you are good enough with a simpler environment? Will you serve dynamic pages or expose a REST api? If you are in the latter case, Django would not be my first choice, there are easier things to look at (I love web.py, FWIW).
Tornado sounds like a good choice if you are looking at async code too, anyway it's hard to give an answer without knowing more about your requirements.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I need to create 2 level web-system. I choose Python as my tool.
I want use PyQt to develop 1st level: TCP/IP-server, and Django as 2nd level: Data visualization through Ajax(Front-End). System sketch on picture:
http://i.stack.imgur.com/pprv9.jpg
1st level will "chat" with about 1000 objects. And web-app with about 200 people.
Is it right way to use Python, Django and PyQt? Or may be there is better architecture solution?
While PyQt's networking module provides tools for writing TCP servers, I'm not sure you really need that dependency, since TCP servers can be written just in Python using only the standard library, and in fact Python already comes with a simple HTTP server built-in (and so does Django, by the way).
I have nothing against PyQt (quite the contrary, I like it a lot), but mixing its programming model and idioms into a Python program has to be done for a reason, and a network server isn't IMHO a good enough reason. If you want a GUI, then sure. But for a network server, just stick with Python, which has some incredibly powerful libraries of its own for writing servers, the foremost being Twisted, which you should definitely check out.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm new to web-application development, and I've just started building a (relatively large) webapp. Thus-far I've been using Django, however, I've just read about Pyramid, and I really like the sound of it: Its documentation reads well, it seems to scale easily from small-to-large projects, it boasts great performance, and it's developers seem quite onto-it. All good things. It also seems quite flexible, which suits my needs well. However, I'm worried about Pyramid's user-base.
For instance, on stackoverflow, the "pyramid" tag has seen 6 questions this week, whereas the "django" tag has seen 247. I know that Pyramid developers are committed to answering any questions developer's have, however, that doesn't completely put my mind at ease. I'm just not sure if I'll be running risks by choosing a framework which has such a drastically smaller community. My fears are this:
Not much "user" documentation
With Django, you can google how to do pretty much anything you want and you'll end up with a tutorial on somebody's blog somewhere in the world.
My fear is that even though the Pyramid documentation seems quite comprehensive, the moment you end up in territory not covered by the documentation, you're kind of on your own (until you submit a question and receive a response, which seems like a much more lengthy process than just reading a blog).
What if it disappears?
Django isn't going anywhere. I don't know enough about Pyramid to make the same assumption. What if I spend a year developing and maintaining this application, only to find out that in the meantime Pyramid support has died out, merged into a different project, etc.?
Hiring future developers for my app - most likely they will know Django, not Pyramid.
Maybe this won't be a huge issue if Pyramid has a relatively small learning curve for people who already know Django?
There might be other serious draw-backs that I'm not aware of for using a framework with such a young community.
Anyway, I'd love if an experienced developer could give me some feedback about all of this. How much of a risk would I be taking by choosing Pyramid over Django? and more generally, by choosing a newer technology over an older one?