[Zope3-Users] Re: zopeproject 0.4: using without easy_installing, egg-info error
Philipp von Weitershausen wrote: > Yes, I've run into that before as well. As Stefan already pointed out, > virtualenv [1] is great way to create a "virtual" Python installation > that behaves like a Python installation except that it's just a bunch of > symlinks and *won't* modify the global installation. > > This is how I do it (virtualenv.py is from the virtualenv tarball): > > $ python virtualenv.py env > ... > $ cd env > $ bin/easy_install zopeproject > ... > $ bin/zopeproject HelloWorld > > > [1] http://cheeseshop.python.org/pypi/virtualenv The other difficulty is that my system (Gentoo ~x86) is python-2.5, and so I am obliged to use the non-system python in any case. The above would work for this. Is there a pro/con list to including a bootstrap.py in zopeproject for the other way of using buildout? Thanks. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: zopeproject 0.4: using without easy_installing, egg-info error
Jeff Kowalczyk wrote: I would like to use zopeproject without easy_installing zopeproject and dependencies into the system python. Yes, I've run into that before as well. As Stefan already pointed out, virtualenv [1] is great way to create a "virtual" Python installation that behaves like a Python installation except that it's just a bunch of symlinks and *won't* modify the global installation. This is how I do it (virtualenv.py is from the virtualenv tarball): $ python virtualenv.py env ... $ cd env $ bin/easy_install zopeproject ... $ bin/zopeproject HelloWorld [1] http://cheeseshop.python.org/pypi/virtualenv -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: zopeproject 0.4: using without easy_installing, egg-info error
Jeff Kowalczyk wrote: Philipp von Weitershausen wrote: Yes, I've run into that before as well. As Stefan already pointed out, virtualenv [1] is great way to create a "virtual" Python installation that behaves like a Python installation except that it's just a bunch of symlinks and *won't* modify the global installation. This is how I do it (virtualenv.py is from the virtualenv tarball): $ python virtualenv.py env ... $ cd env $ bin/easy_install zopeproject ... $ bin/zopeproject HelloWorld [1] http://cheeseshop.python.org/pypi/virtualenv The other difficulty is that my system (Gentoo ~x86) is python-2.5, and so I am obliged to use the non-system python in any case. The above would work for this. I wouldn't recommend using system python anyway. Is there a pro/con list to including a bootstrap.py in zopeproject for the other way of using buildout? I don't quite understand. zopeproject works completely without needing bootstrap.py. After calling zopeproject, you end up with a completely bootstrapped *and* installed buildout sandbox. -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: zopeproject 0.4: using without easy_installing, egg-info error
Philipp von Weitershausen wrote: >> Is there a pro/con list to including a bootstrap.py in zopeproject for the >> other way of using buildout? > > I don't quite understand. zopeproject works completely without needing > bootstrap.py. After calling zopeproject, you end up with a completely > bootstrapped *and* installed buildout sandbox. This non-system python-2.4.4 has an empty site-packages, and is owned by root. I don't have setuptools or buildout installed in the non-system python. When working with a z3c.formdemo checkout for example, I can start: # /opt/python24/python/bin/python bootstrap.py Without using sudo. That bootstrap process creates a local bin/buildout, uses setuptools and zc.buildout from ~/.buildout/eggs, and the non-system python: #!/opt/python24/python/bin/python import sys sys.path[0:0] = [ '/home/myuser/.buildout/eggs/setuptools-0.6c7-py2.4.egg', '/home/myuser/.buildout/eggs/zc.buildout-1.0.0b30-py2.4.egg', ] import zc.buildout.buildout if __name__ == '__main__': zc.buildout.buildout.main() I'm going to familiarize myself with virtualenv; I haven't yet only because the above method seemed both convenient and clear about its use of python environment and eggs. Thanks. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: zopeproject 0.4: using without easy_installing, egg-info error
Jeff Kowalczyk wrote: Philipp von Weitershausen wrote: Is there a pro/con list to including a bootstrap.py in zopeproject for the other way of using buildout? I don't quite understand. zopeproject works completely without needing bootstrap.py. After calling zopeproject, you end up with a completely bootstrapped *and* installed buildout sandbox. This non-system python-2.4.4 has an empty site-packages, and is owned by root. I don't have setuptools or buildout installed in the non-system python. When working with a z3c.formdemo checkout for example, I can start: # /opt/python24/python/bin/python bootstrap.py Without using sudo. That bootstrap process creates a local bin/buildout, uses setuptools and zc.buildout from ~/.buildout/eggs, and the non-system python: Yes, I'm quite familiar with bootstrap.py. It's from a completely different use case, though. With z3c.formdemo, you checkout an existing buildout directory, bootstrap it and then execute the buildout. With zopeproject, you actually have a tool that creates all that buildout boilerplate for you, then automatically bootstraps the buildout and executes it. zopeproject is a tool. For that to work, zopeproject needs to be installed first. Before any of the buildout stuff happens. So you're going to have to easy_install it somehow. If you'd rather not, that's fine. But then you don't get to use that tool. I'm going to familiarize myself with virtualenv; I haven't yet only because the above method seemed both convenient and clear about its use of python environment and eggs. I'm not sure what there is to familiarize with. I pretty much spelled it out for you how to use virtualenv. From an earlier email (virtualenv.py is from the virtualenv tarball): $ python virtualenv.py env ... $ cd env $ bin/easy_install zopeproject ... $ bin/zopeproject HelloWorld This should be easy enough to try out in 2 minutes, probably less time than it took you and me to write these emails. -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
