The declaration-syntax warnings in the zope.interface 4.0.0 are
annoying and mostly pointless.
There will be enough pain in porting applications to Python 3,
avoiding the surprise of having to use a different
interface-declaration syntax will not be of any consequence.
While the deprecation
On Sat, May 19, 2012 at 5:59 PM, Tres Seaver tsea...@palladion.com wrote:
On 05/19/2012 12:12 PM, Jim Fulton wrote:
The declaration-syntax warnings in the zope.interface 4.0.0 are
annoying and mostly pointless.
There will be enough pain in porting applications to Python 3,
avoiding the
This is the summary for test reports received on the
zope-tests list between 2012-05-18 00:00:00 UTC and 2012-05-19 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:
On 05/19/2012 07:23 PM, Jim Fulton wrote:
On Sat, May 19, 2012 at 5:59 PM, Tres Seaver tsea...@palladion.com
wrote:
On 05/19/2012 12:12 PM, Jim Fulton wrote:
The declaration-syntax warnings in the zope.interface 4.0.0 are
annoying and mostly pointless.
There will be enough pain in porting
On Sun, May 20, 2012 at 12:08 AM, Tres Seaver tsea...@palladion.com wrote:
On 05/19/2012 07:23 PM, Jim Fulton wrote:
...
I'd forgotten the fail silently bit. Can't we make the fail loudly
for Python 3?
They already do: 4.0.0 makes them exceptions under Python3: that fact
was actually my
On 05/19/2012 09:00 PM, Zope tests summarizer wrote:
[1]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2012-May/063250.html
[2]FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2012-May/063252.html
