21 thoughts on “Easily install all Python versions under Linux and OSX using collective.buildout.python”

1. http://minitage.org is able to do that about a year or two. You should try it and contact the author on #plone : kiorky

2. Note that to check if PIL is installed properly, you should also try ‘import _imaging’. If that fails, then Plone can start up, but when uploading a picture it will not be converted to the various sizes (thumbnail, preview, etc).

3. Hello, just a little correction, the minitage’s python can also support sqlite, bdb and all other python official extensions that canno’t be well supported if you don’t have installed the prerequisites on your system, system wide.

   The built python is also built with -rpath ensuring that you won’t have to play with LD_LIBRARY_PATH at runtime.

   But minitage also offers system isolation and project deployment consistency (among OSes and projects).

   As it is related to plone, among minitage, we, at makina also use collective.generic.* packages. The goal of thoses package is to deploy in an unique way our portals, no matter their underlying needs. You click & play in the web ront end, and it generates a portal tarball including the uber buildout, the policy & the theme which will do your project born.

   See http://pypi.python.org/pypi/collective.generic.webbuilder/.

4. stevew@stevew-laptop:~/python$ python bootstrap.py
   Traceback (most recent call last):
   File “bootstrap.py”, line 113, in
   ws.find(pkg_resources.Requirement.parse(requirement)).location
   AttributeError: ‘NoneType’ object has no attribute ‘location’

5. I think this is usually because Python setuptools (easy_install command) shipped with your OS is too old.

   Try this:

   easy_install -U setuptools # sudo if needed

6. If you want to build Python on Linux using system libraries try this buildout instead:

   https://svn.plone.org/svn/collective/buildout/bda-naked-python/

   Here are some instructions:

   http://permalink.gmane.org/gmane.comp.web.zope.plone.product-developers/4966

7. This will also be useful for folks who need 2.5 for Google App Engine (it’s not in Lucid Lynx either)

8. Re: ws.find bug: Fixed by Wichert: https://bugs.launchpad.net/zc.buildout/+bug/410528

   I hit same bug using bda-naked-python.

9. Pingback: Running 32-bit chroot on 64-bit Ubuntu server to reduce Python memory usage | mFabrik - web and mobile development

10. What about libxml2 dependencies of Marshaller? Can this way to install make it automatic?

11. http://pypi.python.org/pypi/z3c.recipe.staticlxml/0.7.1

12. Thanks!

    I get:

    ~/PYTHON_VIRTUALENV/python/python-2.4# ./bin/python
    Python 2.4.6 (#1, Aug 4 2010, 14:42:18)
    [GCC 4.3.2] on linux2
    Type “help”, “copyright”, “credits” or “license” for more information.
    >>> import PIL
    >>> import _imaging
    Traceback (most recent call last):
    File “”, line 1, in ?
    ImportError: libjpeg.so.8: cannot open shared object file: No such file or directory
    >>>

    so I think something went wrong.

13. http://plone.293351.n2.nabble.com/Python-buildout-on-Ubuntu-10-04-import-imaging-failing-due-to-libjpeg-td5104024.html

14. ~/PYTHON_VIRTUALENV/python# find . | grep libjpeg.so
    ./python-2.4/lib/libjpeg.so.8.0.2
    ./python-2.4/lib/libjpeg.so.8
    ./python-2.4/lib/libjpeg.so
    ./python-2.5/lib/libjpeg.so.8.0.2
    ./python-2.5/lib/libjpeg.so.8
    ./python-2.5/lib/libjpeg.so
    ./python-2.6/lib/libjpeg.so.8.0.2
    ./python-2.6/lib/libjpeg.so.8
    ./python-2.6/lib/libjpeg.so
    ./parts/opt/lib/libjpeg.so.8.0.2
    ./parts/opt/lib/libjpeg.so.8
    ./parts/opt/lib/libjpeg.so

    so they are there.. now pypi is down and I cannot try any more 🙁

15. Just Do This:
    echo ‘/usr/local/lib’ >> /etc/ld.so.conf

16. Hi,

    Do you know any way to set LD_LIBRARY_PATH during the compilation time? So that buildout would work without changing your system or shell settings?

17. You can use -rpath to free you from using ld_library_path at runtime.
    See:
    – http://en.wikipedia.org/wiki/Rpath_%28linking%29
    – http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html

    Basicly if you have something like this:
    – /bar/include/foo.h
    – /bar/lib/liba.so

    And your target installation path is “/foo”

    Do something like that:
    export CFLAGS=”$CFLAGS -I/bar/include”
    export LDFLAGS=”$LDFKAGS -Wl,-rpath -Wl,/foo -Wl,-rpath -Wl,/bar -L/bar”

    If you want to embed that with buildout, you can have a look to minitage.recipe.cmmi & minitage.recipe.common.

18. Everytime i try to run bin/buildout i keep getting.

    An internal error occured due to a bug in either zc.buildout or in a
    recipe being used:

    Any clue why this happens?

19. try run bin/buildout -vvv

    Also the exception traceaback above that line is important.

    The error message you pasted tells “error happened” but not “which error happened”

20. Thanks Mikko for me it worked very well on my Debian Lenny 😉

21. Since now everything is at github, I think you could edit your post and add the link https://github.com/collective/buildout.python instead of the subversion one. 🙂