On Nov 27, 2007, at 4:54 PM, Mike Orr wrote:
> > James was trying for an idea of putting the egg cache in version > control and letting the deployment copy get all the eggs from the > cache. I assume he also put the buildout inside the Pylons > application. But this causes a chicken-and-egg problem if the Pylons > app does not exist yet and you need to create the buildout in order to > get Paster to create the app to put the buildout in. I guess you need > a separate Pylons buildout for creating applications with. > > Virtualenv seems to have the same problem: you can't put a virtualenv > in an application if the application doesn't exist yet, and you can't > create an empty application directory because "paster create" fails if > the directory exists. What I did was to create a venv named after the > application, install ipython and Pylons, create the app, and continue > using the same venv. > > I think we're going to have to make a simpler buildout lite or enhance > virtualenv with at least an egg cache and probably some other things. > I'm still not sure how to structure the application and venv/buildout > in SVN so I'm keeping the venv in another non-VC directory for now. > But this poses problems down the road when people want a single script > to replicate their environment. Maybe virtualenv's bootstrapping > feature will be sufficient; I'm not sure. Eggs and other big chunks of binary data obviously don't belong in version control. Neither does a virtualenv/buildout really, so having to bootstrap the virtual environment first just has to suffice for now. Apparently Eby wants to add virtual environment management to setuptools 0.7, see: http://mail.python.org/pipermail/distutils-sig/2007-October/008343.html Unfortunately we can't expect this from him any time soon. If setuptools did a virtual environment and also had an egg cache it'd remind me of a simpler Java Maven for Python (which is a good thing). Adding an egg cache to virtualenv in the meantime would be handy. > > Virtualenv also doesn't have a way to update all packages at once. > Maybe that will be OK if people list all their dependencies in > setup.py, but it's easy to forget that. And again it doesn't help for > things like ipython that aren't a package dependency but you still > want them installed anyway. > Updating all eggs would be another nice addition to setuptools itself. A separate script that did this (via setuptools/ pkg_resources) would only be a few lines of code. IPython is a bit like nosetests -- you want to depend on them in testing environments, but usually you wouldn't need them on production. If only we had a way of distinguishing between these types of dependencies (which is another Maven feature). -- Philip Jenvey --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
