Tres Seaver a écrit :
[...]
- Zope 2.10.11,
http://www.zope.org/Products/Zope/2.10.22
short typo :
- Zope 2.10.11,
http://www.zope.org/Products/Zope/2.10.11
--
html
head
/head
body bgcolor=#ff text=#00
img alt=Encolpe Degoute lt;encolpe.dego...@quadra-informatique.frgt
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
discuss
.
Is it the good way to deal with escaping data ?
Or is this a bug of zc.buildout ?
Regards,
--
Encolpe DEGOUTE
http://encolpe.wordpress.com/
http://encolpe.degoute.free.fr/
Logiciels libres, hockey sur glace et autres activités cérébrales
___
Zope-Dev maillist
Sidnei da Silva a écrit :
On 11/13/06, Encolpe Degoute [EMAIL PROTECTED] wrote:
Hello Sidney,
you made a great work but I found two littles things:
In test.py it should be better to save current dir before launching them:
@pushd .
@cd %INSTANCE_HOME%
RUN_COMMAND
@popd
@endlocal
Why
:
In test.py it should be better to save current dir before launching them:
@pushd .
@cd %INSTANCE_HOME%
RUN_COMMAND
@popd
@endlocal
In second, I didn't find runzeo.bat and zeoservice.py I gave you when I
create a zeo instance.
Regards,
--
Encolpe Degoute
INGENIWEB (TM) - S.A.S 5 Euros - RC B 438
compatibility. Maybe this is the
| same as what you call Zope 5, maybe not.
I vote for this one.
There's already Five product to help Zope2 products to become to be
Zope3 compatible. Now, it's to Zope2 developpers to do the
migration step.
- --
Encolpe Degoute
INGENIWEB (TM) - S.A.S 5 Euros - RC B
with Zope products (usual pydoc
doesn't too).
How can I make a fixure to get it working ? Did any of you succeed
documenting Zope products with epydoc ?
I Use HappyDoc, and i have patch it.
I wait for the maintener apply the pacth in the cvs.
Amelioration: Dia, DocBook output.
--
Encolpe
