Here lies the branch:
http://svn.zope.org/repos/main/zope.browser/branches/publisher_definition/
Changes have been rolled back accordingly.
Cheers
- Souheil
2011/3/24 Jim Fulton :
> On Thu, Mar 24, 2011 at 4:14 PM, Souheil CHELFOUH wrote:
>> Thank you for taking the time to answer, Jim.
>>
>> T
On Thu, Mar 24, 2011 at 4:14 PM, Souheil CHELFOUH wrote:
> Thank you for taking the time to answer, Jim.
>
> The work, according to its descriptive nature, was done on the trunk.
> I can revert the change and make a branch, if that's more appropriate
> for this kind of evolution.
> No problem.
Pl
Thank you for taking the time to answer, Jim.
The work, according to its descriptive nature, was done on the trunk.
I can revert the change and make a branch, if that's more appropriate
for this kind of evolution.
No problem.
- Souheil
2011/3/24 Jim Fulton :
> On Thu, Mar 24, 2011 at 12:17 PM, S
On Thu, Mar 24, 2011 at 12:17 PM, Souheil CHELFOUH wrote:
> Hello,
>
> I've been working a lot on zope.publisher lately, trying to extract
> its essence to make my own publisher and flatten the publication
> process.
> This led me to the prototyping of some essential components I wanted
> to facto
Hello,
I've been working a lot on zope.publisher lately, trying to extract
its essence to make my own publisher and flatten the publication
process.
This led me to the prototyping of some essential components I wanted
to factor out of zope.publisher.
Mainly, these are definitions, aka interfaces,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/24/2011 07:57 AM, Zope Tests Summarizer wrote:
> Subject: FAILED : Zope Buildbot / zope2.14-py2.6 slave-ubuntu32
> From: jdriessen at thehealthagency.com
> Date: Wed Mar 23 16:02:31 EDT 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-
On 24 March 2011 12:57, Zope Tests Summarizer wrote:
...
> Test failures
> -
>
> Subject: FAILED : Zope Buildbot / zope2.14-py2.6 slave-ubuntu32
> From: jdriessen at thehealthagency.com
> Date: Wed Mar 23 16:02:31 EDT 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036
Am 24.03.2011 um 12:57 schrieb Zope Tests Summarizer:
[...]
> Subject: FAILED : winbot / z3c.recipe.paster_py_265_32
> From: buildbot at winbot.zope.org
> Date: Thu Mar 24 00:02:42 EDT 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036064.html
I fixed this test in r121107.
Your
Summary of messages to the zope-tests list.
Period Wed Mar 23 12:00:00 2011 UTC to Thu Mar 24 12:00:00 2011 UTC.
There were 89 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 24 from
buildbot at winbot.zope.org, 8 from ccomb at free.fr, 45 from jdriessen at
thehealthagency.com.
Test fai
Hi Uli,
I am happy that some people started to look what is needed to make
modular component registrations with py.test.
The long explanation that you wrote made it easy for me to jump into
funcargs.
Those last months, I have been diving into the great plone.testing
package written by Martin
Hi there,
[extensive introduction by Uli of zope.pytest]
Thanks Uli for that introduction to the package and its problems!
I've been using zope.pytest within 2 Grok projects so far to test
through webob some JSON webservices, and it's worked well for me. I
hadn't had to deal with the issue of
Hello,
* Adam GROSZER [2011-03-23 08:45]:
> On Wed, 23 Mar 2011 07:43:26 +0100 you wrote:
> > On a tangentially-related note, what happened to the proposed new
> > summarizer formatting? Half a year ago (or whenever), I got the
> > impression it was going to be ready "in a few days", but it seems
Hi.
Disclaimer: I don't know anything about pytest.
On Thu, Mar 24, 2011 at 1:05 AM, Uli Fouquet wrote:
> Are there cheap/fast ways to cache/restore registry setups we hadn't had
> on the screen? Really fast setups/cache-restores could make even
> function-wise registrations a considerable thing
13 matches
Mail list logo
