On Mon, Jan 4, 2010 at 12:38 AM, Alex Clark wrote:
> Also, there are a few installation issues (fixed by running `mkdir -p` by
> hand):
> http://pastie.org/765137
> http://pastie.org/765140
On a closer look, this error puzzling me. The "var" and its sub-folders are
already existing in the
Hi Alex,
Thanks for the feedback. I will look into the bugs you pointed out.
On Mon, Jan 4, 2010 at 12:38 AM, Alex Clark wrote:
[snip]
> Another obvious question (sorry ;-), why not just contribute to ZopeSkel
> (which is currently
> in need of some active contributors, IIRC)?
I fel
Hi,
> So here's my proposed solution for the ZTK shrinking issue:
>
> The ZTK branch 'faassen-smaller' contains Hanno's smaller ZTK. Since
> Zope 2 forked the ZTK in response and continued to make changes to their
> fork, I've tried to keep it in sync with the Zope 2 fork.
>
> I've created a new '
Martijn Faassen wrote:
> What lowered the quality of this discussion? I think it is because
> various people became quite upset and annoyed. That's because I reverted
> Hanno's changes to the ZTK trunk. I shouldn't have done that just like
> that, but I needed the subsequent discussion to come up
Martijn Faassen wrote:
> Hi there,
>
> This is a summary of the previous discussions for those who weren't
> paying attention last week and don't want to read a huge thread coming
> back from vacations. I'm talking about you in particular, other steering
> group members. I'll spread it out over mul
Martijn Faassen wrote:
> Martin Aspeli wrote:
> [snip]
>> We've had good success with
>> http://pypi.python.org/pypi/collective.recipe.sphinxbuilder
>
> I'm having trouble with this. I'm trying to set up a "narrative_docs"
> directory in a package but:
>
> * the documentation on collective.recipe.s
I agree and support Martijn's strategy.
There are *many* Zope 3 users who are not visible on this discussion.
For example, these CMS are based on Zope 3, as you can find the word on the
page.
http://z3ext.net/news/z3ext-1_0_0-released/
https://makunouchi.jp/products
Not only them, but more Zope
On Sun, Jan 3, 2010 at 6:43 PM, Chris McDonough wrote:
> Yeah. I haven't thought about this much, so it might be bollocks, but I
> think something like this is what I'm after:
>
> .. code-block-setup::
>
> import sys
> from somepackage.testing import DummyModule
> sys.modules['models'] = Du
Lennart Regebro wrote:
> On Sun, Jan 3, 2010 at 23:14, Benji York wrote:
>> In both of those cases normal doctest blocks seem appropriate.
>
> Not if you don't want the output in the formatting, or if you don't
> want the >>> brackets.
>
Yeah. I haven't thought about this much, so it might be
On Sun, Jan 3, 2010 at 23:38, Benji York wrote:
> I just took a stab at removing all references to zope.testing.doctest
> from Manuel and got it to work using the zope.testing trunk (Manuel
> needs DocTestFailureException).
Awesome! That would make it easy to port to Python 3, which I need.
--
On Sun, Jan 3, 2010 at 23:14, Benji York wrote:
> In both of those cases normal doctest blocks seem appropriate.
Not if you don't want the output in the formatting, or if you don't
want the >>> brackets.
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 6
On Sun, Jan 3, 2010 at 6:53 AM, Martijn Faassen wrote:
> Lennart Regebro wrote:
> [snip]
>> Also if the above code is deemed as being a Good Idea, I will remove
>> all the usage of zope.testing.doctest from Manuel. This is necessary,
>> as one of the things I need from Manuel is a Python 3 port, a
On Sun, Jan 3, 2010 at 4:48 PM, Lennart Regebro wrote:
> On Sun, Jan 3, 2010 at 22:08, Benji York wrote:
>> Occasionally you want to show some code but hide the assertions about
>> the effects of the code. You can do that by putting the tests in a reST
>> comment after the code.
>>
>> .. code-bl
On Wed, Dec 30, 2009 at 7:45 AM, Marius Gedminas wrote:
> On Wed, Dec 30, 2009 at 08:58:52AM +0100, Lennart Regebro wrote:
>> On Tue, Dec 29, 2009 at 23:47, Marius Gedminas wrote:
>> > * support for the INTERPRET_FOOTNOTES feature
>>
>> Then they should use Manuel.
>
> Good, so we have a migrati
On Sun, Jan 3, 2010 at 10:27 PM, Martijn Faassen wrote:
> This is definitely frustrating. :) I want to document something about
> this so that people have more guidance and that our ZTK packages have a
> similar documentation structure,...
So far it seems manuel, the ztk docs and Zope2 all basica
On Sun, Jan 3, 2010 at 22:08, Benji York wrote:
> Occasionally you want to show some code but hide the assertions about
> the effects of the code. You can do that by putting the tests in a reST
> comment after the code.
>
> .. code-block:: python
>
> a = Foo()
> b = a.bar()
>
> .. make sure
Martin Aspeli wrote:
[snip]
> We've had good success with
> http://pypi.python.org/pypi/collective.recipe.sphinxbuilder
I'm having trouble with this. I'm trying to set up a "narrative_docs"
directory in a package but:
* the documentation on collective.recipe.sphinxbuilder pypi talks about
a bi
On Sat, Jan 2, 2010 at 8:44 PM, Chris McDonough wrote:
> Python samples in Sphinx docs are generated like so:
>
> .. code-block:: python
>
> a == 1
>
> I did a bit of fooling around with Manuel, because I wanted to make sure that
> the code blocks in my documentation actually worked, but I wou
On Sat, Jan 2, 2010 at 2:21 PM, Martijn Faassen wrote:
> It'd also be interesting to explore using Manuel - how would one add
> manuel-based testing to a Sphinx documentation tree? I'd like to give
> the priority to testing documentation samples as opposed to
> doctest-driven testing.
The Manuel
Hi there,
So here's my proposed solution for the ZTK shrinking issue:
The ZTK branch 'faassen-smaller' contains Hanno's smaller ZTK. Since
Zope 2 forked the ZTK in response and continued to make changes to their
fork, I've tried to keep it in sync with the Zope 2 fork.
I've created a new 'zope
Hi there,
A meta-discussion, how dangerous! Let's see whether it can help us
improve the way we work together, though.
I'll talk about how I think, from my perspective, we can improve the
quality of discourse on this mailing list and be more constructive.
What lowered the quality of this discu
Hi there,
This is a summary of the previous discussions for those who weren't
paying attention last week and don't want to read a huge thread coming
back from vacations. I'm talking about you in particular, other steering
group members. I'll spread it out over multiple short mails.
So what hap
Hey,
Roger wrote:
> Since aaron added new mimetypes e.g. application/javascript,
> the _implicitResult method in zope.publisher.http.py (line 794)
> is broken because the method checks for text/* content types
> if unicode is given:
>
> def _implicitResult(self, body):
> encoding = g
On 2010-01-03, Baiju M wrote:
> On Sun, Jan 3, 2010 at 9:20 PM, Andreas Jung wrote:
>> How is this different from ZopeSkel?
>
> Well, it's just yet another PasteScript project template. BlueBream
> provides a slightly different layout compared to "basic_zope" .
Another obvious question (sorry ;-
On Sun, Jan 3, 2010 at 9:20 PM, Andreas Jung wrote:
> How is this different from ZopeSkel?
Well, it's just yet another PasteScript project template. BlueBream
provides a slightly different layout compared to "basic_zope" .
Here are few features:
1. BlueBream project package includes ZTK + few a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
> Hi All,
> I started a project named "BlueBream" to create a
> script to setup a Zope project directory. BlueBream use
> ZTK with some additional packages. BlueBream is
> based on PasteScript's template plugin.
>
> The packag
Hi All,
I started a project named "BlueBream" to create a
script to setup a Zope project directory. BlueBream use
ZTK with some additional packages. BlueBream is
based on PasteScript's template plugin.
The package is available from PyPI:
http://pypi.python.org/pypi/bluebream
Source cod
Summary of messages to the zope-tests list.
Period Sat Jan 2 12:00:00 2010 UTC to Sun Jan 3 12:00:00 2010 UTC.
There were 6 messages: 6 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Sat Jan 2 20:38:00 EST 2010
URL: http://
Lennart Regebro wrote:
[snip]
> Also if the above code is deemed as being a Good Idea, I will remove
> all the usage of zope.testing.doctest from Manuel. This is necessary,
> as one of the things I need from Manuel is a Python 3 port, and I'm
> not porting zope.testing.doctest to Python 3.
I think
On Sun, Jan 3, 2010 at 02:44, Chris McDonough wrote:
> But I couldn't really figure out a way to do the moral equivalent of this:
>
> .. code-block:: python
>
> a == 1
>
> .. manuel-expect:
>
> True
>
> Maybe I missed it.
I couldn't either. So I added a sphinx module for Manuel, supporting
30 matches
Mail list logo
