[Distutils] entry point for new installations?

[Kevin Dangoor]

Someone just prodded me about automatic application reloading, which
is always a hairy topic. The autoreload code that many people run in
development mode forks to run the actual application in a child
process, and everything in sys.modules is watched for a change. If one
of the files change, the child exits and the parent process fires off
a new one. It's ugly, but it's reliable and is generally fine for
development.

For TurboGears apps, I'm of the opinion that the right way to deploy
an app to production is to turn it into an egg and install it. I had
the (not entirely fleshed out) thought that it might be interesting if
there was an entry_point that got called when new eggs were installed.
This would make it possible to notify a running server that it needs
to be restarted.

Thoughts?

Kevin

--
Kevin Dangoor
Author of the Zesty News RSS newsreader

email: kid at blazingthings.com
company: http://www.BlazingThings.com
blog: http://www.BlueSkyOnMars.com