collective/buildout.python

Various errors with buildout > 1.4.4

Closed this issue · 10 comments

This ticket now tracks the buildout issues brought up in #16, #20 and #21.

Using the old bootstrap and buildout 1.4.4 seems to fix all of them, I'm currently testing that for a while. Also see #16 (comment)

Just a 'me too'.

I have switched from Mac Snow Leopard to Mountain Lion this week. The standard bootstrap indeed gives problems. I no longer have the error messages, but when building 3.3 it was something like SyntaxError 'exec value' in parts/buildout/site.py. When building 2.7 it was "parts/buildout/site.py does not start with any of these prefixes". The python I used for running the bootstrap was /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python. Using 2.6 gave the same problems.

And bootstrap-1.4.4.py solves it, so +1 for making that the default.

I have tested it for a while now and there seem to be no issues using the older buildout. Alex Clark reverted to the old one already. This ticket stays open until there is a buildout version which fixes the site.py issue.

Great, thanks. Still trying to figure out where the generated site.py comes from in Buildout 1.5.x and 1.6.x so we can remove "with f" in 1.6.x (while we wait for Buildout 2, in which it's been removed) CC: @iElectric

Roger, will take a peek.

So we have two bugs:

  • under python2.4 site.py fails due to usage of with statement
  • under all python versions virtualenv fails due to prefix mismatch -> did anyone dig more into this issue?

Regarding bug 2, can someone try with git master of virtualenv?

FWIW, from #buildout:

15:59 < J1m> mgedmin, I encourage you to use 
  https://github.com/downloads/buildout/buildout/bootstrap.py 
  instead
15:59 < J1m> in fact, everyone here should.

That means we should test that bootstrap.py to see if it resolves the issues mentioned here, I think.

I call shenanigans: everyone knows that #buildout is Freenode's 2nd most silent channel.

Not anymore! It's active-ish now

I'm assuming this one is stale, or wontfix.