originally we did your approach, but now we use multiple discrete packages, 
and manage the virtualenv with fabric

|python_packages/
|     |----app_pyramid/
|     |          |---setup.py
|     |          |---app_pyramid/
|     |----app_core/
|     |          |---setup.py
|     |          |---app_core/
|     |----app_celery/
|     |          |---setup.py
|     |          |---app_celery/
|     |----app_model/
|     |          |---setup.py
|     |          |---app_model/
|fabfile.py

the fabric file is used to manage everything and proxy commands to 
setup.py/pip/etc. it can build packages as needed, install from source, or 
even deploy into select environments.


-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/24488b66-9416-4d95-9bd0-e14096af63e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to