Encolpe Degoute wrote:
> Can I add it in the trunk or does anybody want a branch ?
Do it on a branch, even if it seems trivial. At least you'll want to run
the tests on different systems before modifying the trunk, which will be
easier when you can check the changes out from a branch.
--
Thomas
Thomas Lotze a écrit :
> Encolpe Degoute wrote:
>
>> As zc.buildout is using something near string.template I patched
>> gocept.recipe.env to replace '$' by '$$' and collective.recipe.template to
>> replace '$$' by '$'.
>
> For the record: gocept.recipe.env hasn't yet been patched; I'd rather
> d
Encolpe Degoute wrote:
> As zc.buildout is using something near string.template I patched
> gocept.recipe.env to replace '$' by '$$' and collective.recipe.template to
> replace '$$' by '$'.
For the record: gocept.recipe.env hasn't yet been patched; I'd rather
discuss the issue first before applyi
Shameless plug: try z3c.recipe.filetemplate.
http://pypi.python.org/pypi/z3c.recipe.filetemplate
. Sounds like it does what you want out of the box.
Gary
On Aug 27, 2009, at 9:14 AM, Encolpe Degoute wrote:
> Hello,
>
> These last days I was using collective.recipe.template and
> gocept.rec
On Thu, Aug 27, 2009 at 9:14 AM, Encolpe Degoute wrote:
> Hello,
>
> These last days I was using collective.recipe.template and
> gocept.recipe.env.
>
> The second one just update options with os.environ.
> Unix shell having their own substitution methods then '${' appearing in
> the .installed.cfg
Hello,
These last days I was using collective.recipe.template and
gocept.recipe.env.
The second one just update options with os.environ.
Unix shell having their own substitution methods then '${' appearing in
the .installed.cfg. It just blows if you try to rerun 'bin/buildout.
As zc.buildout is