Hi I came across something surprising recently that made me scratch my head and want to understand more deeply the relationship between paster, your pylons code, and python.
I added some code to the destructor of my Globals object. This code waits 10 seconds, in a timing loop, and then prints a message. When I kill paster with Ctrl-c, it returns to the C: prompt. 10 second later, this message is printed out. I concluded that something other than the paster executable is "running" my pylons code. I suspected it must be an instance of Python, and when I look at Task Manager I can confirm this. Does anyone know any of the details of how python, paster, and your pylons code is related? Here's what I think I know: - You start "paster serve xxx.ini" and somehow an instance of python is launched - I'm tempted to say that somehow paster then asks/causes the python instance to fully execute your pylons executable and thus the python instance will stay running until all your threads in your pylons app are done. - Is this even close to right? - So when I do a ctrl-c, to stop paster, who is getting the ctrl-c and acting on it? Paster or python? - If paster is effectvely "starting python" and having it execute your pylons app, why does paster continue to run as an executable once it's gotten everything started i.e., what could it be doing once python is executing your pylons app? Any insights here could clear a lot of things up for me! Thanks! Michael -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
