Hi,
for some reason chameleon.zpt gives the following output:
html
head
...
/head/htmlheadgt;
body
...
/body/htmlgt;
The template seems fine, anybody seen that before?
Christian
--
Christian Theune · c...@gocept.com
gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany
Lennart Regebro wrote:
On Sun, Apr 5, 2009 at 17:23, Tres Seaver tsea...@palladion.com wrote:
PyPI won't work for non-eggified products.
Right, so they need to be eggified then, which is a Good Thing. :)
I'm not saying they should be moved *now*. Just in the long run. If
the product is
Laurence Rowe wrote:
Previously Marius Gedminas wrote:
BTW I've yet to see a firewall that blocks SSH. Am I lucky?
Yes. Blocking ssh is very common in larger companies in me experience.
An ssh server running on port 443 (HTTPS) can come in very handy. ssh -D
gives you a socks proxy,
We're using zope.documenttemplate for ArchGenXML code generation.
If we feed it with unicode-strings it breaks while joining its rendered
parts, see http://zope3.pov.lt/trac/browser/zope.documenttemplate/trunk/
src/zope/documenttemplate/pdocumenttemplate.py#L335
I know, DTML is rarely used,
Hanno Schlichting wrote:
Dieter Maurer wrote:
Unless newer SVN versions improved on this: using different
access protocols is hampered by svn:external as they were (still
are?) required to be absolute urls (including the protocal).
This way, the access protocol may change in between of a
2009/4/6 Chris Withers ch...@simplistix.co.uk:
Laurence Rowe wrote:
Previously Marius Gedminas wrote:
BTW I've yet to see a firewall that blocks SSH. Am I lucky?
Yes. Blocking ssh is very common in larger companies in me experience.
An ssh server running on port 443 (HTTPS) can come in
On Mon, Apr 6, 2009 at 10:32, Chris Withers ch...@simplistix.co.uk wrote:
Just beware, 1.5 sucks:
http://subversion.tigris.org/issues/show_bug.cgi?id=3242
http://thread.gmane.org/gmane.comp.version-control.subversion.user/84308/focus=84019
Martijn Pieters wrote:
On Mon, Apr 6, 2009 at 10:32, Chris Withers ch...@simplistix.co.uk wrote:
Just beware, 1.5 sucks:
http://subversion.tigris.org/issues/show_bug.cgi?id=3242
http://thread.gmane.org/gmane.comp.version-control.subversion.user/84308/focus=84019
Previously Martijn Pieters wrote:
On Mon, Apr 6, 2009 at 10:32, Chris Withers ch...@simplistix.co.uk wrote:
Just beware, 1.5 sucks:
http://subversion.tigris.org/issues/show_bug.cgi?id=3242
http://thread.gmane.org/gmane.comp.version-control.subversion.user/84308/focus=84019
On Mon, Apr 6, 2009 at 10:39, Chris Withers ch...@simplistix.co.uk wrote:
I'm more worried about the lack of merging working and random errors
when adding files. Those are pretty serious failures from where I'm
sitting...
The merging is due to lack of merging info when branching, the 'random
Hi,
Christian Theune wrote:
for some reason chameleon.zpt gives the following output:
html
head
/head/htmlheadgt;
body
/body/htmlgt;
The template seems fine, anybody seen that before?
As with all bug reports, exact version numbers (including the lxml
version) and the
Hello Christian,
Roger found a bug with z3c.form recently too regarding z3c.pt.
Monday, April 6, 2009, 9:41:42 AM, you wrote:
CT Hi,
CT for some reason chameleon.zpt gives the following output:
CT html
CT head
CT ...
CT /head/htmlheadgt;
CT body
CT ...
CT /body/htmlgt;
CT The template
Martijn Pieters wrote:
On Mon, Apr 6, 2009 at 11:53, Wichert Akkerman wich...@wiggy.net wrote:
Note that we are now up to svn 1.6.
Which still does not fix this, and is preventing people from upgrading
to the 1.5 client, and thus from using checkouts using relative paths.
Bugger, that is
On Mon, Apr 6, 2009 at 11:53, Wichert Akkerman wich...@wiggy.net wrote:
Note that we are now up to svn 1.6.
Which still does not fix this, and is preventing people from upgrading
to the 1.5 client, and thus from using checkouts using relative paths.
Bugger, that is indeed correct. I may not
On Mon, Apr 6, 2009 at 10:16, Chris Withers ch...@simplistix.co.uk wrote:
Lennart Regebro wrote:
On Sun, Apr 5, 2009 at 17:23, Tres Seaver tsea...@palladion.com wrote:
PyPI won't work for non-eggified products.
Right, so they need to be eggified then, which is a Good Thing. :)
I'm not
2009/4/3 Roger Ineichen d...@projekt01.ch:
Can you run the group.txt tests in z3c.form and confirm the
issue. A
div tag get skipped after some nested repeat tags. (line 898, in
group.txt)
I've reproduced this bug in a test case in ``chameleon.zpt`` (r4073).
Will try and solve asap; thanks
Lennart Regebro wrote:
The alternative is to make a new products directory on zope.org, which
is of course completely possible.
Well, I know what Andreas is planning to do is moving the whole thing to
old.zope.org and then using rewrite rules to redirect any 404's from
www.zope.org to there.
2009/4/3 Roger Ineichen d...@projekt01.ch:
Can you fix this or give me some hints which let me do this?
This issue has been fixed and ``chameleon.core`` 1.0b27 released.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Tres Seaver wrote:
Lennart Regebro wrote:
On Sun, Apr 5, 2009 at 08:32, Dieter Maurer die...@handshake.de wrote:
Because members put there content (product implementations) still usable?
Absolutely right. In the long run that
On Mon, Apr 6, 2009 at 15:21, Chris Withers ch...@simplistix.co.uk wrote:
Sure. But I don't really see it as necessary to keep old.zope.org
around forever and ever.
Some people do, and doing that means they're happy, so I'm happy :-)
Fair enough. The correct path is I guess as always that
On Mon, Apr 6, 2009 at 10:14, Chris Withers ch...@simplistix.co.uk wrote:
PyPI will work in exactly the same way as zope.org for non-eggified
products: manual download.
What I *would* worry about is non-egg distributions on PyPI causing
problems for setuptools and its ilk...
Wouldn't
Previously Chris Withers wrote:
Tres Seaver wrote:
KGS the
concept is very easy to implement; you just make available on some URL a
buildout versions.cfg, or you run your own package index.
OK, the former I can see happening on an end-user project, the latter is
just too much work.
On Apr 4, 2009, at 12:56 PM, Chris Withers wrote:
Hey All,
http://pypi.python.org/pypi/zdaemon indicates that zdaemon is alpha.
I would have though it would be marked as stable, given how long its
been around?
Is there a reason for that?
Extra meta data is hard to maintain. We shouldn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
On Mon, Apr 6, 2009 at 15:21, Chris Withers ch...@simplistix.co.uk wrote:
Sure. But I don't really see it as necessary to keep old.zope.org
around forever and ever.
Some people do, and doing that means they're happy, so I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Previously Chris Withers wrote:
Tres Seaver wrote:
KGS the
concept is very easy to implement; you just make available on some URL a
buildout versions.cfg, or you run your own package index.
OK, the former I can see
Michael Haubenwallner wrote:
Some people do, and doing that means they're happy, so I'm happy :-)
Fair enough. The correct path is I guess as always that those who want
to keep it get to be responsible for maintaining it. Problem solved.
:)
I won't support anything called 'old.zope.org'.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
Tres Seaver wrote:
Roger Ineichen wrote:
Log message for revision 97754:
Use applySkin from new location zope.publisher.skinnable
instead of zope.publisher.browser.
This change breaks older packages who might expect
On Mon, Apr 6, 2009 at 11:47 AM, Baiju M mba...@zeomega.net wrote:
On Mon, Apr 6, 2009 at 12:46 AM, Michael Howitz m...@gocept.com wrote:
Am 05.04.2009 um 22:00 schrieb Baiju M:
In reStructuredText, I think two colons :: is required to make it
source text ?
No, double colons mark literal
On Mon, Apr 6, 2009 at 11:56 AM, Benji York be...@zope.com wrote:
On Mon, Apr 6, 2009 at 11:47 AM, Baiju M mba...@zeomega.net wrote:
On Mon, Apr 6, 2009 at 12:46 AM, Michael Howitz m...@gocept.com wrote:
Am 05.04.2009 um 22:00 schrieb Baiju M:
In reStructuredText, I think two colons :: is
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Previously Chris Withers wrote:
Tres Seaver wrote:
KGS the
concept is very easy to implement; you just make available on some URL
a
buildout versions.cfg, or you run your own
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Previously Chris Withers wrote:
Tres Seaver wrote:
KGS the
concept is very easy to implement; you just make available
On Mon, Apr 6, 2009 at 2:19 PM, Baiju M mba...@zeomega.net wrote:
On Mon, Apr 6, 2009 at 11:56 AM, Benji York be...@zope.com wrote:
[snip]
Please see http://mail.zope.org/pipermail/zope-dev/2008-August/033010.html
So we should not use either single colon (:) or indent doctest ?
Single colons
On Mon, Apr 6, 2009 at 11:47 AM, Baiju M mba...@zeomega.net wrote:
Why we cannot use literal blocks for source code ?
From the above documentations, I can see that it works for doctest.
And we have used it in many places. Also in PyPI
(long_description), it looks better.
Because reST
On Apr 6, 2009, at 9:28 AM, Chris Withers wrote:
Gary Poster wrote:
Sadly, I suspect none of the tools are as advanced as TortoiseSVN.
Which
is a real shame :-( Perforce maybe? ;-)
Fair enough that bzr didn't take your fancy, but FWIW, did you try
TortoiseBzr? That has received love
34 matches
Mail list logo