On Tue, Apr 10, 2012 at 9:58 AM, Graham Dumpleton <[email protected]> wrote: > You probably don't want to create a system which is wedded to how > Apache works. You would be much better off fully drinking the cool aid > as to how Python web applications work and go use a proper Python web > framework. This will save you a lot of trouble in the end. > > A simple framework to get you started would be Flask (flask.pocoo.org).
As I said earlier, this is just for fun. I used Django and recently Flask for real stuff ;) This also grow from my frustration getting our new hires (a php developer) getting up to speed with python development. We used django at work and things that we python developers take for granted took lot of time for them to comprehend. Most of it relate back to understanding how python import work and also the difference between stateless nature of PHP and long running python process. It seem easy to us but not to them. On the import issue, it also caused by django manipulating the path (thank god it's gone now in 1.4) it's not clear to them what happen under the hood when running through manage.py runserver and why django wsgi script in the documentation doesn't work and they have to fix it to add path to their lib into sys.path. In the end, they simply ask why so much trouble ? -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
