On Wednesday, February 27, 2013 08:55:21 AM Marius Gedminas wrote:
> > [6]winbot / z3c.form_py_265_32
> > [7]winbot / z3c.form_py_265_32
> > [8]winbot / z3c.formui_py_265_32
>
> Same: failure to build lxml.
z3c.form used to pin lxml 2.3, which I did not even see on PyPI anymore.
Unfo
On Wed, Feb 27, 2013 at 08:55:21AM +0200, Marius Gedminas wrote:
> > [3]Still Failing - zopetoolkit_trunk_app - Build # 167
>
> Build #168:
>
> /tmp/hudson2996479762744665535.sh: 1: ./bin/test-zopeapp: not found
Given http://zope3.pov.lt/trac/changeset/129871/zopetoolkit (aka "remove
all t
On Wed, Feb 27, 2013 at 01:00:01AM +, Zope tests summarizer wrote:
> [1]FAILED (failures=1) : Zope-trunk Python-2.7.3 : Linux
Failure in test test_combined_scored_search_planned
(Products.ZCatalog.tests.test_catalog.TestScoring)
Traceback (most recent call last):
File
"/home/stefan/aut
This is the summary for test reports received on the
zope-tests list between 2013-02-25 00:00:00 UTC and 2013-02-26 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/
On Tuesday, February 26, 2013 01:00:39 PM Tres Seaver wrote:
> > * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.)
>
> AFAIK, the remaining test failures on Py33 are largely spurious (doctest
> repr issues, or else are pending the fork to use 'zodbpickle'.
So the state here is:
- W
On Tue, Feb 26, 2013 at 6:12 PM, Stephan Richter
wrote:
> Could you outline what the first step would be to create an alpha release list
> for 2.0? We could manually include an sdist of the ZODB 4 py3 branch to make
> the tests pass under Python 3.
I'll have to look at the procedure again a bit.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/2013 10:46 AM, Stephan Richter wrote:
> Even though, most ported packages are fully Python 3 compatible, they
> might depend on packages that are not ready to get a final release.
> Those two are:
>
> * zope.security 4.0.0 (pending PyPy suppo
On Tue, Feb 26, 2013 at 08:48:10AM -0500, Stephan Richter wrote:
> This brings up a bigger question:
>
> Even though, most ported packages are fully Python 3 compatible, they might
> depend on packages that are not ready to get a final release. Those two are:
>
> * zope.security 4.0.0 (pending P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/2013 11:04 AM, Hanno Schlichting wrote:
> My goals for a 2.0 release would be (comparing to
> http://docs.zope.org/zopetoolkit/releases/overview-1.1.html):
>
> - Drop support for Python 2.5 (ZTK 1.1 still supports that)
+1.
> - Add support
On Tuesday, February 26, 2013 05:04:26 PM Hanno Schlichting wrote:
> Contrary to wait I said before I'd be willing to work on a ZTK 2.0
> release (knowing the tools and procedure).
Could you outline what the first step would be to create an alpha release list
for 2.0? We could manually include an
Hi.
The process for a ZTK 2.0 release isn't really well defined. I'm not
sure if Jan-Wijbrand and Christophe are still interested in working on
ZTK releases.
Contrary to wait I said before I'd be willing to work on a ZTK 2.0
release (knowing the tools and procedure).
My goals for a 2.0 release w
On Tuesday, February 26, 2013 02:41:02 PM Marius Gedminas wrote:
> This error is caused by zope.publisher 4.0.0a1:
>
> bin/buildout -n buildout:prefer-final=false buildout:versions=versions \
>versions:zope.publisher='<4.0.0a1' \
>versions:zope.session='<4.0.0a1'
Hi everyone,
what is the process to start working on ZTK 2.0? We are about 5-6 packages
away from porting ZTK to Python 3 and I would like to start working on a new
release.
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
___
On Tue, Feb 26, 2013 at 02:41:02PM +0200, Marius Gedminas wrote:
> On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote:
> > > [5]winbot / z3c.contents_py_265_32
> > > [6]winbot / z3c.contents_py_265_32
> >
> > There's this lovely bit at the beginning I don't remember from befor
On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote:
> > [5]winbot / z3c.contents_py_265_32
> > [6]winbot / z3c.contents_py_265_32
>
> There's this lovely bit at the beginning I don't remember from before,
> but it's not counted as a test failure:
>
> ZopeXMLConfigurationError
On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote:
> On Tue, Feb 26, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
> > [5]winbot / z3c.contents_py_265_32
> > [6]winbot / z3c.contents_py_265_32
>
> There's this lovely bit at the beginning I don't remember from before,
16 matches
Mail list logo
