Can PyAMF support service deployment by way of the filesystem?
I use PyAMF together with Django. A possible solution could roughly look like this:

Create a python module containing all your different AMF services py files
Create a view that wrapps the DjangoGateway and initialize all your services. Inside this view you could do the following:  


reload() your service module
populate a dictionary based on i.e. the file names ({SERVICE_NAME: SERVICE_INSTANCE})
Instantiate DjangoGateway with this dictionary and let it handle the incoming request.


This is a hackish solution based on the fact that you can only deploy files without any additional actions like restarting a server.
I'm evaluating PyAMF to replace our current PHP (ugh) AMF services framework, and I'm unable to find the one crucial piece of information that would allow me to provide a compelling use case for changing over:
Right now, new PHP AMF services are deployed simply by putting the .php files in the filesystem; the next time they're accessed, the new service is in play. Removal of a service is as simple as deleting the .php file that provided it, and updating it is correspondingly simple. I need that same ease-of-deployment from PyAMF. If we have to rewrite our installers to deploy these services, it'll be a nonstarter.
So, what I need to know is, can PyAMF support new service discovery by way of the filesystem, can it support service upgrading and removal by way of same, and if so, what is the best way to set it up to do this?
I'm open to any of the various server options; I can easily have cherrypy, django, whatever installed and running on its own, and even -- with a bit more sturm nd drang -- have mod_python or mod_wsgi made available.