Buildout

support environment variables as part of option values

Bug #557769 reported by Florian Friesdorf
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Buildout
New
Undecided
Unassigned

Bug Description

I implemented support for environment variables as option values.

One patch is for enabling ${env:<variable>} syntax, wherever ${<section>:<option>} is supported. The value of an environment variable may contain a reference to a section:option. (0001-...)

The other patch enables usage of ${env:<variable>} for extends. (0002-...)

Tests are included, patches apply cleanly to 1.4.3 and trunk@110428

Revision history for this message
Florian Friesdorf (flo-chaoflow) wrote :
Revision history for this message
Florian Friesdorf (flo-chaoflow) wrote :
Revision history for this message
Florian Friesdorf (flo-chaoflow) wrote :

aclark pointed me to gocept.recipe.env which might be a cleaner approach, however, without support for extends. On the other hand, the extends support is unrelated to the support everywhere else.

Revision history for this message
Marc Abramowitz (msabramo) wrote :

I love this idea. This would make it easy to share my ~/.buildout/default.cfg file between systems.

Revision history for this message
Alexandre Fayolle - camptocamp (alexandre-fayolle-c2c) wrote :

The problem with the gocept recipe is that I cannot use it to set things in the [buildout] section as this causes:

    Error: Referenced option does not exist: env HOME

I'm trying to setup a the shared egg directory in a portable way via .buildout/default.cfg

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.