You need to run the create-plone-bootstrap.py with a python which has virtualenv and setuptools already installed.
It generates plone-try-bootstrap.py, which you can run with a python with neither virtualenv or setuptools:
python_with_tools create-plone-bootstrap.py
python_without_tools plone-try-boostrap.pyThere's an example of this flow in doit.sh (with a path to a "virgin" python with no setuptool or virtualenv installed).
Currently it's hardcoded to use buildout 1.4.4.
The virtualenv is built into .plone_python, and the buildout get's built into bin.
- runs buildout bootstrap after it installs it.
- doesn't re-virtualenv if you're already in a virtualenv
- checks for python < 2.6 and exits
- renamed the bootstrap.py's -v (or --version) flag (which specifies which version of zc.buildout to install to -b and --buildout_version (which defaults to 1.4.4 for the time being)
This is a work in progress in response to this email by Alex Limi ( on behalf of Martin Aspeli):
Sending this on behalf of Martin, since he has to leave for his flight back
to the UK:
All,
Problem #1 for new users on Unix platforms: Using a non-isolated system
Python.
We're now in a position where most Linux and Mac users will have a binary
called python2.6 in their path, so we can have instructions like::
$ python2.6 bootstrap.py
$ bin/buildout
Yay. Except if you do that with a Python you didn't compile yourself, it
explodes in weird and wonderful ways. Compiling/installing your own Python
is a significant barrier (I witnessed this for about 1/3rd of the people in
my training course). And of course, this happens every time Limi tries to
do anything Plone-related.
A good-enough solution for most people is to use virtualenv. So now, our
instructions become::
$ sudo easy_install -U virtualenv
$ virtualenv -p /usr/bin/python2.6 --no-site-packages ~/python
$ ~/python/bin/python bootstrap.py
$ bin/buildout
So, here's the rub: We can do this for people in the ``bootstrap.py``.
Right
now, people just download the one from http://python-distribute.org, or copy
one from another buildout. So, what if we had::
$ python2.6 plone-bootstrap.py
$ bin/buildout
This would:
* Sniff out a half-decent Python
* Install virtualenv (ideally without needing sudo access)
* Create a virtualenv without site packages, e.g. in a ``.python``
directory
* Use its isolated python to do what bootstrap does now, so
``bin/buildout``
uses this
Some key constraints/requirements
* It has to be a single file - no package you install with setuptools
* It has to be cross-platform (including Windows, Linux, Mac)
* It should ideally not require a buildout.cfg in the current directory, as
bootstrap.py does
* It needs to print meaningful error messages if it can't figure out what
to do in the environment
* It may need some kind of knowledge of Plone versions to understand which
Python versions are compatible
Regards,
Martin
--
Alex Limi · +limi <http://profiles.google.com/limi> · @limi · limi.net