On 02/28/2013 08:00 AM, Marius Gedminas wrote:
On Thu, Feb 28, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
An error occurred when trying to install coverage 3.5.3. Look above this
message for any errors that were output by easy_install.
error: Setup script exited with error: command
On Thu, Feb 28, 2013 at 8:00 AM, Marius Gedminas wrote:
> On Thu, Feb 28, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
>> [3]UNKNOWN : Zope-trunk Python-2.6.8 : Linux
>> [4]UNKNOWN : Zope-trunk Python-2.7.3 : Linux
>
> Something new:
>
> Zope-trunk Python-2.6.8 : Linux (x86_6
On Thursday, February 28, 2013 09:00:30 AM Marius Gedminas wrote:
> > [9]winbot / z3c.form_py_265_32
> > [10] winbot / z3c.formui_py_265_32
>
> No lxml on winbot
So we have to solve this issue. I cannot declare lxml=2.3 anymore, because
only lxml 3.0+ supports Python 3. If we want to keep
On Thu, Feb 28, 2013 at 07:15:57AM -0500, Stephan Richter wrote:
> On Thursday, February 28, 2013 09:00:30 AM Marius Gedminas wrote:
> > > [9]winbot / z3c.form_py_265_32
> > > [10] winbot / z3c.formui_py_265_32
> >
> > No lxml on winbot
>
> So we have to solve this issue. I cannot declare l
Hi everyone,
I would like to deprecate zope.sequencesort in ZTK 2.0, since it cannot
properly ported to Python 3, since it depends heavily on the cmp() way of
sorting. I am also not a user of the package and I only tried to port the
package for completeness sake.
Thoughts?
Regards,
Stephan
--
On Thu, Feb 28, 2013 at 2:43 PM, Stephan Richter
wrote:
> I would like to deprecate zope.sequencesort in ZTK 2.0, since it cannot
> properly ported to Python 3, since it depends heavily on the cmp() way of
> sorting. I am also not a user of the package and I only tried to port the
> package for co
On Feb 28, 2013, at 14:43 , Stephan Richter wrote:
> Hi everyone,
>
> I would like to deprecate zope.sequencesort in ZTK 2.0, since it cannot
> properly ported to Python 3, since it depends heavily on the cmp() way of
> sorting. I am also not a user of the package and I only tried to port the
On Thursday, February 28, 2013 02:59:33 PM Hanno Schlichting wrote:
> In the same way, I think we should remove RestrictedPython and
> zope.untrustedpython from the ZTK. Since those are also very much
> dependencies of Zope alone and porting is going to be a very
> challenging task.
Well, it is us
On Thu, Feb 28, 2013 at 3:00 PM, Wichert Akkerman wrote:
>
> On Feb 28, 2013, at 14:43 , Stephan Richter wrote:
>
>> Hi everyone,
>>
>> I would like to deprecate zope.sequencesort in ZTK 2.0, since it cannot
>> properly ported to Python 3, since it depends heavily on the cmp() way of
>> sorting.
On Thu, Feb 28, 2013 at 09:00:30AM +0200, Marius Gedminas wrote:
> On Thu, Feb 28, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
> > [1]Still Failing - zopetoolkit_trunk - Build # 186
>
> Same six failures, caused by
>
> ImportError: No module named persistent
>
> inside BTrees.
Hi all,
I went through the ztk-versions.cfg file and verified availability of a Python
3
port. I commented the ztk-versions.cfg file. Below are the relevant sections.
If we remove all deprecated pacakges and packages that should not be in use
anymore, only the following dependencies/toolchain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2013 08:43 AM, Stephan Richter wrote:
> Hi everyone,
>
> I would like to deprecate zope.sequencesort in ZTK 2.0, since it
> cannot properly ported to Python 3, since it depends heavily on the
> cmp() way of sorting. I am also not a user of th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2013 10:41 AM, Lennart Regebro wrote:
> Reading through the code, it seems to use a lot of code to provide
> quite basic sorting functionality. It feels like it's trying to fill
> the same role as sorted() does since Python 2.4.
The other
On Thursday, February 28, 2013 11:32:26 AM Tres Seaver wrote:
> > Thoughts?
>
> I'm generally in favor of shrinking the ZTK, but just for discussion's
> sake: emulating 'cmp' for objects which have rich comparison semantics
> isn't that difficult::
>
> def _faux_cmp(lhs, rhs):
> return i
Hi,
On Thu, Feb 28, 2013 at 1:30 PM, Stephan Richter
wrote:
> [...]
> # XXX: Where is this needed?
> unittest2 = 0.5.1
You probably already know all this, but for those that simply copied
what was done in other packages for cargo-cult programming reasons:
unittest2 is a backport of Python 2.7+
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2013 01:04 PM, Stephan Richter wrote:
> On Thursday, February 28, 2013 11:32:26 AM Tres Seaver wrote:
>>> Thoughts?
>>
>> I'm generally in favor of shrinking the ZTK, but just for
>> discussion's sake: emulating 'cmp' for objects which have
This is the summary for test reports received on the
zope-tests list between 2013-02-27 00:00:00 UTC and 2013-02-28 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 Thu, Feb 28, 2013 at 5:33 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/28/2013 10:41 AM, Lennart Regebro wrote:
>
>> Reading through the code, it seems to use a lot of code to provide
>> quite basic sorting functionality. It feels like it's trying to fill
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2013 10:00 PM, Lennart Regebro wrote:
> On Thu, Feb 28, 2013 at 5:33 PM, Tres Seaver
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 02/28/2013 10:41 AM, Lennart Regebro wrote:
>>
>>> Reading through the code, it seems t
New issues:
- ZTK drops zope.untrustedpython, zope.pagetemplate pulls it back in
- zope.testbrowser.wsgi disappeared?!
The usual suspects:
- lxml for Windows
- authentication: str vs unicode
- newlines on Windows: should page templates normalize to \n?
- z3c.recipe.paster still fragile
20 matches
Mail list logo
