Buildout

script_initialization ignored if executable has broken -S

Bug #756841 reported by nutjob
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Buildout
New
Undecided
Unassigned

Bug Description

A number of recipes (zc.recipe.testrunner, plone.recipe.zope2instance, etc.) generate scripts with optional environment variables or other initialization code. Such code gets passed to the function zc.buildout.easy_install.sitepackage_safe_scripts in the ``script_initialization`` parameter.

However, if the buildout's executable has a broken -S implementation (as evidenced by the call to _has_broken_dash_S returning True), any value in ``script_initiazliation`` is ignored out as control flow goes to the _original_scripts_function. There's no notice or warning to the user.

All recipes that rely on script_initialization are affected.

Revision history for this message
Ford Guo (agile-guo) wrote :

Yeah,I have the same problem,initialization and environment can not work.
my env: buildout 1.5.2

Revision history for this message
goibhniu (cillian-deroiste) wrote :

Reverting to zc.buildout 1.4 (by changing the bootstrap.py: http://svn.zope.org/repos/main/zc.buildout/branches/1.4/bootstrap/bootstrap.py) is one way to work around this.

Revision history for this message
Robert Niederreiter (rnix) wrote :

I ran into the same problem.

adding a 2-liner in L1264:

if script_initialization and not initialization:
    initialization = script_initialization

... would do the job, not sure if this is the right way to fix though

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.