On Jun 16, 7:32 pm, Gustavo Narea <gustavona...@2degreesnetwork.com> wrote: > Hello. > > On 16/06/10 01:33, Graham Dumpleton wrote: > > > Paste has its own problems. Paste server itself does process > > environment setup that isn't done by other WSGI hosting mechanisms. > > Specifically, it initialises Python logging in a way suited to Paste > > based applications. Like with Django development server, you can > > develop a Paste based application on Paste server which will then not > > work on other WSGI hosting mechanisms. > > Paste Script will set up logging its way if and only if you explicitly > tell it to; i.e., defining logging configuration in the Paste Deploy > file or passing an argument to `paster'. I cannot think of another thing > that it does at startup time which may affect deployment, but I may be > wrong.
But that will not happen if you use a different hosting mechanism. Thus you end up with a fiddle as documented in: http://wiki.pylonshq.com/display/pylonscookbook/Logging+under+mod_wsgi The point I am making is that these hosting system specific fiddles should never need to be done by a user. Graham > I think there's always the risk of things working on a development > server but not on the production environment, but the thing is how that > risk can be minimized. > > > > > > > There certainly is a larger problem I also want to address beyond > > pointing out the issues with Django deployment, but I haven't even > > mentioned them in these posts and don't intend to. > > > What you are trying to do with using Paste Script/Deploy is tinkering > > at the edges of a larger issue you probably don't even know exists or > > don't appreciate. Paste Script/Deploy will not solve that larger issue > > as there are lots of things it doesn't do. Adopting it will only make > > it harder to solve the real problems later on. > > > Trying to address the bigger issue is going to need some cooperation > > between all frameworks and hosting solution authors to come up with a > > consistent way of doing certain stuff. Right now though I don't have > > time to lay out properly what the issues are or implement a proof of > > concept which illustrates the direction one could take to solve the > > problem. It may be the case that Paste Script/Deploy could be adapted > > to meet that requirement at some point, but by itself, because the > > focus of Paste Deploy is more about constructing WSGI components > > together to create an application, as opposed to solving the problem > > of deployment on a specific hosting mechanism, I feel right now it is > > a poor choice. > > > If time allows I hope to talk to Russell about some of this stuff when > > he is at PyCon in Sydney, but it will still need a lot more work after > > that. > > > Ultimately if something doesn't get done to address the bigger issues, > > the WSGI deployment (distinct from composing together WSGI components > > into an application), will continue to be a dogs breakfast. > > I have no idea what those problems are, so I never meant to solve them. > I just found two issues and Paste Deploy/Script seemed like a solution. > > I'm curious about them though. I'll keep an eye on your blog and Web-SIG. > > -- > Gustavo Narea. > Software Developer. > 2degrees, Ltd. <http://www.2degreesnetwork.com/>. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
