On Sat, Apr 17, 2010 at 06:34, Martin Aspeli optilude+li...@gmail.com wrote:
Hi Lennart co,
On 17 April 2010 02:38, Lennart Regebro rege...@gmail.com wrote:
On Fri, Apr 16, 2010 at 19:53, Jonathan Lange j...@mumak.net wrote:
As the author of one of those other testrunners, I can tell you
On Sat, Apr 17, 2010 at 03:41, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This kind of goes with Lennart's frustration about trying to port the
ZTK packages, or a core subset, to Python 3.
I would like to see the ZTK packages have really excellent
(Although possible we could call it developing instead of hacking
but that's not a big issue. ;) )
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
___
Zope-Dev maillist - Zope-Dev@zope.org
On 2010-4-17 03:41, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This kind of goes with Lennart's frustration about trying to port the
ZTK packages, or a core subset, to Python 3.
I would like to see the ZTK packages have really excellent
documentation, as well as 100%
Hi!
Tres Seaver wrote:
The refactoring I would like to see happen is to move the main narrative
documentation into a separate, Sphinx-driven 'docs' directory in each
ZTK package. As part of this move, we can start adding some of the
really nice Sphinx features (cross references, indexing,
On Sat, Apr 17, 2010 at 11:18, yuppie y.2...@wcm-solutions.de wrote:
How can we make sure docs and code don't get out of sync? Do we have to
run unittests *and* build the docs before each checkin? Will someone
make sure buildbots and nightly tests report broken docs as well?
Hm... As long as
Summary of messages to the zope-tests list.
Period Fri Apr 16 12:00:00 2010 UTC to Sat Apr 17 12:00:00 2010 UTC.
There were 14 messages: 6 from Zope Tests, 7 from ccomb at free.fr, 1 from ct
at gocept.com.
Test failures
-
Subject: FAILED: Repository policy check found errors in 668
On 17 April 2010 10:41, Lennart Regebro rege...@gmail.com wrote:
On Sat, Apr 17, 2010 at 11:18, yuppie y.2...@wcm-solutions.de wrote:
How can we make sure docs and code don't get out of sync? Do we have to
run unittests *and* build the docs before each checkin? Will someone
make sure buildbots
On Sat, Apr 17, 2010 at 16:05, Laurence Rowe l...@lrowe.co.uk wrote:
It's important that documentation is tested as part of the standard
test run, that means when you change something you know to update the
docs. repoze.bfg seemed to make an attempt at this, though it is
currently disabled.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
On Sat, Apr 17, 2010 at 16:05, Laurence Rowe l...@lrowe.co.uk wrote:
It's important that documentation is tested as part of the standard
test run, that means when you change something you know to update the
docs. repoze.bfg
On Sat, Apr 17, 2010 at 19:17, Tres Seaver tsea...@palladion.com wrote:
I'm ambivalent about testing the Sphinx code snippets on each test run.
I want those snippets to be *much* less comprehensive than they are
currently, and am pretty sure that drift in the non-executable bits is
at least
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
On Sat, Apr 17, 2010 at 19:17, Tres Seaver tsea...@palladion.com wrote:
I'm ambivalent about testing the Sphinx code snippets on each test run.
I want those snippets to be *much* less comprehensive than they are
currently,
On Fri, Apr 16, 2010 at 9:41 PM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This kind of goes with Lennart's frustration about trying to port the
ZTK packages, or a core subset, to Python 3.
I would like to see the ZTK packages have really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Fri, Apr 16, 2010 at 9:41 PM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This kind of goes with Lennart's frustration about trying to port the
ZTK packages, or a core subset, to
On 4/17/10 5:20 PM, Tres Seaver wrote:
- Documentation should be written for documentation's sake. The
emphasis should be on helping people understand what the software is
for and how to use it, *not* on coverage.
Amen.
- Documentation should be executable. Manuel helps a lot for this.
Christophe Combelles a écrit :
Roger a écrit :
Hi
Betreff: Re: [Zope-dev] KGS 3.4.1 versions
Adam GROSZER a écrit :
Hello,
There is a sheet with versions for KGS 3.4.1
http://spreadsheets.google.com/pub?key=tUE5Q72d4Kg1FXaacCA3EKQoutput=
html
Anyone for/against those versions?
On 18 April 2010 05:20, Tres Seaver tsea...@palladion.com wrote:
I'm not against having the snippets be executable, because I *do* want
them to work. I just don't want to encourage anyone to think that they
are testing the software when they write the snippets, or execute them.
Executing
17 matches
Mail list logo
