[Zope-dev] chameleon.zpt: broken html output?

2009-04-06 Thread Christian Theune
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
http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1
Zope and Plone consulting and development


signature.asc
Description: This is a digitally signed message part
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] leaving zope.org to work...

2009-04-06 Thread Chris Withers
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 still maintained and cared about, eggifying it and
 moving it to PyPI isn't that much work.
 
 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.

That seems like a double win for me:

- old urls keep working

- no need to add a products sections on www.zope.org

I'm sure Andreas will correct me if I'm wrong when he gets back from his 
holidays...

Chris

-- 
Simplistix - Content Management, Zope  Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Chris Withers
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, tsocks makes using this transparent (e.g. 
 tsocks bin/buildout). Failing that, 3G modems are quite reasonable nowdays.

I'd like to see you do either of these two tricks on a big corporate's 
network, particularly the latter, for any length of time and keep your 
job...

Chris

-- 
Simplistix - Content Management, Zope  Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] zope.documentetemplate breaks with unicode

2009-04-06 Thread Jens W. Klein
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, but for code-generation its fine. Is this a 
bug or does DTML not support unicode?

regards Jens
-- 
Jens W. Klein - Klein  Partner KEG - BlueDynamics Alliance

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Chris Withers
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 checkout
 (involving svn:externals).
 
 svn:externals can be relative in many ways since SVN 1.5.

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
http://thread.gmane.org/gmane.comp.version-control.subversion.user/87346/focus=87525

Chris

-- 
Simplistix - Content Management, Zope  Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Laurence Rowe
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 very handy. ssh -D
 gives you a socks proxy, tsocks makes using this transparent (e.g. tsocks
 bin/buildout). Failing that, 3G modems are quite reasonable nowdays.

 I'd like to see you do either of these two tricks on a big corporate's
 network, particularly the latter, for any length of time and keep your
 job...

Nah, this would only be a problem if you worked with the IT
department, everyone else prefers that you get more work done.
Obviously with the 3G card my laptop was not connected to the network.

Laurence
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Martijn Pieters
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
 http://thread.gmane.org/gmane.comp.version-control.subversion.user/87346/focus=87525

It sucks for very specific cases, namely tight access control on
sub-paths. I don't see such cases, and I see speed improvements
instead.

Note that we are now up to svn 1.6.

-- 
Martijn Pieters
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Chris Withers
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
 http://thread.gmane.org/gmane.comp.version-control.subversion.user/87346/focus=87525
 
 It sucks for very specific cases, namely tight access control on
 sub-paths. 

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...

Chris

-- 
Simplistix - Content Management, Zope  Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Wichert Akkerman
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
  http://thread.gmane.org/gmane.comp.version-control.subversion.user/87346/focus=87525
 
 It sucks for very specific cases, namely tight access control on
 sub-paths. I don't see such cases, and I see speed improvements
 instead.
 
 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.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/   It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Martijn Pieters
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
errors' are not random but due to svn info being out-of-date after a
commit. svn up has always solved that for me. Yes, the latter is a
bug, but I suspect it is already solved in 1.6 (didn't test that yet
though).

-- 
Martijn Pieters
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] chameleon.zpt: broken html output?

2009-04-06 Thread Hanno Schlichting
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 minimal template that causes this would be helpful.
Include a test case and report it at https://bugs.launchpad.net/z3c.pt
and it's likely to get fixed soon ;)

Hanno

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] chameleon.zpt: broken html output?

2009-04-06 Thread Adam GROSZER
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 seems fine, anybody seen that before?

CT Christian



-- 
Best regards,
 Adam GROSZERmailto:agros...@gmail.com
--
Quote of the day:
No goals  No Glory.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Chris Withers
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 indeed correct. I may not have any problems (and a
 workaround for svn bug 3119) but that doesn't mean we can ask other
 people that need access to more tightly ACL-ed repositories to put up
 with subversion 1.5 and 1.6.

To be honest, the state of svn 1.5 is what's getting me to think about 
looking at mercurial.

(bzr didn't take my fancy, and hg is gonna be used by the python-core 
folks, so I might as well learn that...)

Sadly, I suspect none of the tools are as advanced as TortoiseSVN. Which 
is a real shame :-( Perforce maybe? ;-)

Chris

-- 
Simplistix - Content Management, Zope  Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Martijn Pieters
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 have any problems (and a
workaround for svn bug 3119) but that doesn't mean we can ask other
people that need access to more tightly ACL-ed repositories to put up
with subversion 1.5 and 1.6.

-- 
Martijn Pieters
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] leaving zope.org to work...

2009-04-06 Thread Lennart Regebro
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 saying they should be moved *now*. Just in the long run. If
 the product is still maintained and cared about, eggifying it and
 moving it to PyPI isn't that much work.

 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.

Sure. But I don't really see it as necessary to keep old.zope.org
around forever and ever. A couple of years, sure, preferably as
read-only, and with a change in the templates to say that any content
that should be preserved should be moved somewhere else, IMHO.

-- 
Lennart Regebro: Pythonista, Barista, Notsotrista.
http://regebro.wordpress.com/
+33 661 58 14 64
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.pt bug

2009-04-06 Thread Malthe Borch
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 for identifying it.

\malthe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] leaving zope.org to work...

2009-04-06 Thread Chris Withers
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.
 
 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 :-)

Chris

-- 
Simplistix - Content Management, Zope  Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.pt bug

2009-04-06 Thread Malthe Borch
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
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] dispatching zope.org's roles as a download source...

2009-04-06 Thread Tres Seaver
-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 should probably be moved over
 to PyPI though.
 PyPI won't work for non-eggified products.
 
 That's not true...
 
 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...

Exactly:  it would defeat the purpose of putting them there


Tres.
- --
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ2gxJ+gerLs4ltQ4RAg/vAJ9RNMgjH+OGzc/hTWYP6x968ZNtkQCeLn6s
I8LDcy8jz9oQs/2nQAC0ERo=
=gX8L
-END PGP SIGNATURE-
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] leaving zope.org to work...

2009-04-06 Thread Lennart Regebro
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 those who want
to keep it get to be responsible for maintaining it. Problem solved.
:)

-- 
Lennart Regebro: Pythonista, Barista, Notsotrista.
http://regebro.wordpress.com/
+33 661 58 14 64
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] dispatching zope.org's roles as a download source...

2009-04-06 Thread Lennart Regebro
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 easy_install/buildout/etc just fail in those cases? Typically
with a no setup.py found or something?

-- 
Lennart Regebro: Pythonista, Barista, Notsotrista.
http://regebro.wordpress.com/
+33 661 58 14 64
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] setting missing minimum version in setup.py

2009-04-06 Thread Wichert Akkerman
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.
  
  Not really.  Collect the tarballs, run a script, configure Apache to
  serve that diretory. 
 
 Hmm, too much... but is it needed?
 Can you not point index at just a local folder on disk?
 I'm sure the Plone folks did something like this, maybe Hanno can chime in?

What we do is: collect the tarballs, serve the resulting directory. I
have not seen a need to run a script.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/   It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zdaemon is alpha?

2009-04-06 Thread Jim Fulton

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 use Trove  
classifiers for project status.

 If not, I'll change it on trunk...


Please just remove that trove classifier.

Jim

--
Jim Fulton
Zope Corporation


___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] leaving zope.org to work...

2009-04-06 Thread Michael Haubenwallner
-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 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'.

Regards
Michael

- --
http://blog.d2m.at
http://planetzope.org

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ2iuIl0uAvQJUKVYRAjmEAKCG+cIitCfHQoAuRdSV7o5LAUB9nACglMtG
o7MYqPpBA1kwyUnl6oNZH2o=
=HO3T
-END PGP SIGNATURE-

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] setting missing minimum version in setup.py

2009-04-06 Thread Tres Seaver
-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 happening on an end-user project, the latter is 
 just too much work.
 Not really.  Collect the tarballs, run a script, configure Apache to
 serve that diretory. 
 Hmm, too much... but is it needed?
 Can you not point index at just a local folder on disk?
 I'm sure the Plone folks did something like this, maybe Hanno can chime in?
 
 What we do is: collect the tarballs, serve the resulting directory. I
 have not seen a need to run a script.

If you want to an index, rather than just a directory for 'find-links',
you need to create the 'PyPI simple format' directory structure.


Tres.
- --
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ2iu0+gerLs4ltQ4RAsbCAJ9T//C/+Ok1s4VgDQEXcnE+d6LHFQCfVTG8
+nE8OhQjjRncytfdRiDoIkw=
=uXI+
-END PGP SIGNATURE-

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] leaving zope.org to work...

2009-04-06 Thread Chris Withers
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 appreciate all the work you've provided on zope.org (Michael really 
has put a lot of effort into trying to get things sorted when no-one 
else would) but in the instance I see that as a good thing...

Chris

-- 
Simplistix - Content Management, Zope  Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] SVN: zope.traversing/trunk/ Use applySkin from new location zope.publisher.skinnable

2009-04-06 Thread Tres Seaver
-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 a 3.5.x version to
 have compatible dependencies:  it impliictly requires
 zope.component=3.6.0, which is wildly incompatible.  I think the 3.5.3
 release tag should be copied as 3.6.0, and a 3.5.4 should be released
 which reverts this change.
 
 +1

Done.


Tres.
- --
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ2jGD+gerLs4ltQ4RAqY3AJ9PnnS+J9h0gkbd9090h4Q21g8eAwCeNUaP
g+BoZUi+0pb6x+3LM5ffOJ8=
=jS1c
-END PGP SIGNATURE-

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: zope.app.generations/trunk/src/zope/app/generations/README.txt made blocks consistent

2009-04-06 Thread Benji York
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 blocks [1].
 Doctest blocks are marked by  at the beginning of the line. [2]

 [1]
 http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#literal-blocks
 [2]
 http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#doctest-blocks

 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.

Please see http://mail.zope.org/pipermail/zope-dev/2008-August/033010.html

(adding zope-dev and removing checkins)
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: zope.app.generations/trunk/src/zope/app/generations/README.txt made blocks consistent

2009-04-06 Thread Baiju M
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 required to make it
 source text ?

 No, double colons mark literal blocks [1].
 Doctest blocks are marked by  at the beginning of the line. [2]

 [1]
 http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#literal-blocks
 [2]
 http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#doctest-blocks

 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.

 Please see http://mail.zope.org/pipermail/zope-dev/2008-August/033010.html

So we should not use either single colon (:) or indent doctest ?

Regards,
Baiju M
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] setting missing minimum version in setup.py

2009-04-06 Thread Wichert Akkerman
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 package index.
  OK, the former I can see happening on an end-user project, the latter 
  is 
  just too much work.
  Not really.  Collect the tarballs, run a script, configure Apache to
  serve that diretory. 
  Hmm, too much... but is it needed?
  Can you not point index at just a local folder on disk?
  I'm sure the Plone folks did something like this, maybe Hanno can chime in?
  
  What we do is: collect the tarballs, serve the resulting directory. I
  have not seen a need to run a script.
 
 If you want to an index, rather than just a directory for 'find-links',
 you need to create the 'PyPI simple format' directory structure.

What is the advantage of creating an index?

Wichert.

-- 
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/   It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] setting missing minimum version in setup.py

2009-04-06 Thread Tres Seaver
-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 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.
 Not really.  Collect the tarballs, run a script, configure Apache to
 serve that diretory. 
 Hmm, too much... but is it needed?
 Can you not point index at just a local folder on disk?
 I'm sure the Plone folks did something like this, maybe Hanno can chime in?
 What we do is: collect the tarballs, serve the resulting directory. I
 have not seen a need to run a script.
 If you want to an index, rather than just a directory for 'find-links',
 you need to create the 'PyPI simple format' directory structure.
 
 What is the advantage of creating an index?

Not relying on PyPI.


Tres.
- --
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ2krs+gerLs4ltQ4RAty5AKDYSPuvEieNqBm1TnyiNk7ulJzYHwCgugTv
xoKaPWWpvkrVsQH0IqPokCQ=
=YGGd
-END PGP SIGNATURE-

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: zope.app.generations/trunk/src/zope/app/generations/README.txt made blocks consistent

2009-04-06 Thread Benji York
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 are fine, but they don't mean anything to reST (I don't
use them much).

Indenting doctests isn't required, but it is the prevailing style, so
I'd like to keep doing it.
-- 
Benji York
Senior Software Engineer
Zope Corporation
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: zope.app.generations/trunk/src/zope/app/generations/README.txt made blocks consistent

2009-04-06 Thread Zvezdan Petkovic
 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 specification says that they are not doctests any more if  
you use ::.  They are literal blocks in that case.

http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#doctest-blocks

Specifically the sentence: If both are present, the literal block  
syntax takes priority over Doctest block syntax

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Source Code Repository

2009-04-06 Thread Gary Poster


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 relatively recently.


I'm looking at this:

http://bazaar-vcs.org/TortoiseBzr/Screenshots

Where's the visual diff?
Where's the interactive log of revisions?
Where's the repository browser?


FWIW, I don't know if TortoiseBzr has this.  I'd be surprised if it  
didn't have these, especially the first two.  It would be cool if  
someone with easy access to Windows were to check this out.   
Otherwise, I'll give it a try eventually and report back myself.


(If it has these features, I'll try to figure out someone to ask to  
get that page updated.)



Does it work the same on Windows, Ubuntu and Mac OS?


(I assume you mean bzr vs.svn, rather than TortoiseBzr vs.  
TortoiseSvn; AFAICT, Tortoise* is Windows only.)


Well, the EOL problem has been the only bzr kicker there.  That was  
just addressed, spurred most recently in part because of the concerns  
from the Zope community; I don't know if it is in 1.13 or the upcoming  
1.14.  Other than that, I think bzr cares a fair amount about Windows  
(and certainly about Ubuntu and Mac).


http://tortoisesvn.net/image/tid/13 gives a fair idea of the kinds  
of things I'd need to feel compelled to change...


Right.  Looks nice enough.

Gary___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )