Re: [Zope-dev] Class advisors in Python 3

2010-07-30 Thread Hanno Schlichting
On Fri, Jul 30, 2010 at 11:49 PM, Charlie Clark
 wrote:
> ZTK 1.1 deprecates Python 2.4 *and* 2.5. So, 2010-12-31 is the last day
> for their official support.

Who told you that? We documented our decision at
http://docs.zope.org/zopetoolkit/process/python-versions.html.

Python 2.5 is nowhere close to being deprecated.

Hanno
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Class advisors in Python 3

2010-07-30 Thread Charlie Clark
Am 30.07.2010, 13:57 Uhr, schrieb Hanno Schlichting :

> Class decorators were introduced in Python 2.6.
> I think it's going to be a whole before we can require 2.6 as a minimum  
> version.

ZTK 1.1 deprecates Python 2.4 *and* 2.5. So, 2010-12-31 is the last day  
for their official support.

Charlie
-- 
Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] cAccessControl.so Zope 2.12.7

2010-07-30 Thread Christopher Warner
On Fri, Jul 30, 2010 at 4:16 PM, Hanno Schlichting wrote:

> On Fri, Jul 30, 2010 at 10:08 PM, Christopher Warner
>  wrote:
> > Unfortunately in the above specific case I'm building against a
> standalone
> > Plone instance which ships only with a static lib version of Python 2.6.
> So
> > this doesn't work. This became an issue with Plone 4.0b5 as this is the
> > first version to include Zope 2.12.7 egg. The 2.12.6 egg has the correct
> > arch.
> > The only remedy I can readily see is that however cAccessControl.so is
> built
> > needs to be built specifically for the i386 arch and stuffed into the
> egg.
>
> Where are you getting a Zope2 egg from? We only publish a Zope2 source
> release, which you will need to compile yourself for *nix platforms.
> We only provide binary eggs for Windows, which come in both a 32bit
> and 64bit flavor.
>
> I'm guessing you are hitting a problem in the Plone unified installer.
> The correct place to report that is at http://dev.plone.org/plone/.
>
> Hanno
>

Ok thank you sir.

-- 
Christopher Warner
http://cwarner.kernelcode.com
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] cAccessControl.so Zope 2.12.7

2010-07-30 Thread Hanno Schlichting
On Fri, Jul 30, 2010 at 10:08 PM, Christopher Warner
 wrote:
> Unfortunately in the above specific case I'm building against a standalone
> Plone instance which ships only with a static lib version of Python 2.6. So
> this doesn't work. This became an issue with Plone 4.0b5 as this is the
> first version to include Zope 2.12.7 egg. The 2.12.6 egg has the correct
> arch.
> The only remedy I can readily see is that however cAccessControl.so is built
> needs to be built specifically for the i386 arch and stuffed into the egg.

Where are you getting a Zope2 egg from? We only publish a Zope2 source
release, which you will need to compile yourself for *nix platforms.
We only provide binary eggs for Windows, which come in both a 32bit
and 64bit flavor.

I'm guessing you are hitting a problem in the Plone unified installer.
The correct place to report that is at http://dev.plone.org/plone/.

Hanno
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] cAccessControl.so Zope 2.12.7

2010-07-30 Thread Christopher Warner
This is probably an issue with 2.12.7 to 2.12.10 as current. I haven't
tested beyond 2.12.7 however.

The AccessControl module; specifically the shared lib cAccessControl.so as
built on an osx arch x86_64 is incorrect as the runtime expects i386. In
most cases a knowledgable user will able to rebuild this library with
something like:

gcc -dynamic -bundle -arch i386
> -I/Applications/Plone4/Python-2.6/include/python2.6
> -I/Applications/Plone4/buildout-cache/eggs/ExtensionClass-2.13.1-py2.6-macosx-10.4-i386.egg/
> -I/Applications/Plone4/buildout-cache/eggs/Acquisition-2.13.3-py2.6-macosx-10.4-i386.egg/
> /Applications/Plone4/Python-2.6/lib/libpython2.6.a
> /usr/lib/libpython2.6.dylib -L/Applications/Plone4/Python-2.6/lib/
> cAccessControl.c -o cAccessControl.so


Unfortunately in the above specific case I'm building against a standalone
Plone instance which ships only with a static lib version of Python 2.6. So
this doesn't work. This became an issue with Plone 4.0b5 as this is the
first version to include Zope 2.12.7 egg. The 2.12.6 egg has the correct
arch.

The only remedy I can readily see is that however cAccessControl.so is built
needs to be built specifically for the i386 arch and stuffed into the egg.
-- 
Christopher Warner
http://cwarner.kernelcode.com
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.testsetup test faliure (was Re: Zope Tests: 55 OK, 18 Failed)

2010-07-30 Thread Uli Fouquet
Hi Christophe,

Christophe Combelles wrote:

> Thanks for releasing 0.8.1. It seemed to fix it!
> 
> However I have a weird problem: builders were all green, then I suddenly had 
> repeated failures with 0.8.1 on all the builders, then I've tried to launch 
> the 
> tests by myself directly in the builder, and tests passed, without changing 
> anything... Then if I relaunch the builder alone, tests pass:
> http://buildbot.afpy.org/bluebream/waterfall
> 
> Is there a possibility that tests fail when several builders run at the same 
> time?
> 

Yes, and I think for a strange reason: they took to much time (probably
because they share system resources and simply run slower each).

The problem here was, that in the test testrunners are run  and the
regular expressions matching their output did expect output of kind 

  "Total: ... 0 errors in N.NNN seconds"

and not:

  "Total: ... 0 errors in 1 minutes N.NNN seconds"

But that's what happened in buildbot runs: they took more than one
minute to run some subprocesses. On a real slow and old machine you
might be able to reproduce the error :-)

I think there is no need for special configuration or similar.

Instead, I fixed the regular expressions and fixed also some other
things, so that the next release should be okay (also with Python 2.7).

The changes are alreadey checked in, just had no time to do the actual
release. Please expect 0.8.2 this evening.

May I update the bluebream versions.cfg then as well? Until now Baiju
was friendly enough to do that (thanks for that!).

Sorry for the trouble! Hope, there will be less problems then.

Best regards,

-- 
Uli



signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.testsetup test faliure (was Re: Zope Tests: 55 OK, 18 Failed)

2010-07-30 Thread Adam GROSZER
Hello Christophe,

Friday, July 30, 2010, 6:26:47 PM, you wrote:

CC> Is there a possibility that tests fail when several builders run at the 
same time?

I keep them serialized, one after the other just be on the safe side.

-- 
Best regards,
 Adam GROSZERmailto:agros...@gmail.com
--
Quote of the day:
Enjoy yourself because you can't change anything anyway

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.testsetup test faliure (was Re: Zope Tests: 55 OK, 18 Failed)

2010-07-30 Thread Christophe Combelles
> Hi Christophe,
>
> Christophe Combelles wrote:
>
> [snip: z3c.testsetup test errors on bluebream]
>>
>> thanks!! There is only one remaining error on Python 2.4 now. It seems 
>> related
>> to an 'encoding' argument added to DocFileSuite in python 2.5, and used in
>> zope.app.testing
>
> Oh, missed that. This is more tricky but I'll have a look into it.
> Thanks for the hint (and the buildbots revealing such nasty problems)!

Thanks for releasing 0.8.1. It seemed to fix it!

However I have a weird problem: builders were all green, then I suddenly had 
repeated failures with 0.8.1 on all the builders, then I've tried to launch the 
tests by myself directly in the builder, and tests passed, without changing 
anything... Then if I relaunch the builder alone, tests pass:
http://buildbot.afpy.org/bluebream/waterfall

Is there a possibility that tests fail when several builders run at the same 
time?




File 
"/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/README.txt",
 
line 110, in README.txt
Failed example:
 testrunner.run(defaults)
Differences (ndiff with -expected +actual):
 - Running z3c...layer.DefaultZCMLLayer [...ftesting.zcml] tests:
 -   Set up z3c...layer.DefaultZCMLLayer [...ftesting.zcml] in N.NNN 
seconds.
 + Running z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting.zcml]
 
tests:
 +   Set up z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting.zcml]
 
in N.NNN seconds.
 Ran 3 tests with 0 failures and 0 errors in N.NNN seconds.
 - Running z3c...layer.DefaultZCMLLayer [...ftesting2.zcml] tests:
 -   Tear down z3c...layer.DefaultZCMLLayer [...ftesting.zcml] ... not 
supported
 + Running z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting2.zcml]
 
tests:
 +   Tear down z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting.zcml]
 
... not supported
 Running in a subprocess.
 -   Set up z3c...layer.DefaultZCMLLayer [...ftesting2.zcml] in N.NNN 
seconds.
 +   Set up z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting2.zcml]
 
in N.NNN seconds.
 Ran 1 tests with 0 failures and 0 errors in N.NNN seconds.
 -   Tear down z3c...layer.DefaultZCMLLayer [...ftesting2.zcml] ... not 
supported
 +   Tear down z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting2.zcml]
 
... not supported
   Running z3c.testsetup.tests.othercave.testing.FunctionalLayer1 tests:
 Running in a subprocess.
 Set up z3c.testsetup.tests.othercave.testing.FunctionalLayer1 in N.NNN 
seconds.
 Ran 1 tests with 0 failures and 0 errors in N.NNN seconds.
 Tear down z3c.testsetup.tests.othercave.testing.FunctionalLayer1 in 
N.NNN seconds.
   Running z3c.testsetup.tests.othercave.testing.UnitLayer2 tests:
 Running in a subprocess.
 Set up z3c.testsetup.tests.othercave.testing.UnitLayer1 in N.NNN 
seconds.
 Set up z3c.testsetup.tests.othercave.testing.UnitLayer2 in N.NNN 
seconds.
   Running testSetUp of UnitLayer1
   Running testSetUp of UnitLayer2
   Running testTearDown of UnitLayer2
   Running testTearDown of UnitLayer1
 Ran 1 tests with 0 failures and 0 errors in N.NNN seconds.
 Tear down z3c.testsetup.tests.othercave.testing.UnitLayer2 in N.NNN 
seconds.
 Tear down z3c.testsetup.tests.othercave.testing.UnitLayer1 in N.NNN 
seconds.
 - Running zope...testrunner.layer.UnitTests tests:
 ?  ^
 + Running zope.testing.testrunner.layer.UnitTests tests:
 ?  ^^^
 Running in a subprocess.
 -   Set up zope...testrunner.layer.UnitTests in N.NNN seconds.
 ?   ^
 +   Set up zope.testing.testrunner.layer.UnitTests in N.NNN seconds.
 ?   ^^^
 - Custom setUp for  
 - Custom tearDown for  
 + Custom setUp for  
 + Custom tearDown for  
 Ran 4 tests with 0 failures and 0 errors in N.NNN seconds.
 -   Tear down zope...testrunner.layer.UnitTests in N.NNN seconds.
 ?  ^
 +   Tear down zope.testing.testrunner.layer.UnitTests in N.NNN seconds.
 ?  ^^^
 - Total: 10 tests, 0 failures, 0 errors in N.NNN seconds.
 + Total: 10 tests, 0 failures, 0 errors in 1 minutes N.NNN seconds.
 ? ++
   False


>
> Best regards,
>
_

Re: [Zope-dev] zope.testing / zope.testrunner path forward:

2010-07-30 Thread Lennart Regebro
On Tue, Jul 27, 2010 at 13:26, Jonathan Lange  wrote:
> Just to be clear, is zope.testing 4.0.0 intended to work with Python 2?

Yes.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Class advisors in Python 3

2010-07-30 Thread Lennart Regebro
On Fri, Jul 30, 2010 at 13:35, Hanno Schlichting  wrote:
> zope.interface contains 2to3 fixers to rewrite them to a class
> decorator syntax IIRC.

Actually, it's in zope.fixers. :) And it's only implements() ->
@implementor i think. Adapts come with zope.component which isn't
ported to Python 3 yet, but the same thing should happen there, yes.

-- 
Lennart Regebro, Colliberty: http://www.colliberty.com/
Python, Zope, Plone blog: http://regebro.wordpress.com/
Telephone: +33 661 58 14 64
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Zope Tests: 24 OK, 19 Failed, 1 Unknown

2010-07-30 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list.
Period Thu Jul 29 12:00:00 2010 UTC to Fri Jul 30 12:00:00 2010 UTC.
There were 44 messages: 6 from Zope Tests, 1 from buildbot at 
enfoldsystems.com, 4 from buildbot at pov.lt, 13 from buildbot at 
winbot.zope.org, 11 from ccomb at free.fr, 9 from jdriessen at 
thehealthagency.com.


Test failures
-

Subject: FAILED : Bluebream / Python2.4.6 32bit linux
From: ccomb at free.fr
Date: Thu Jul 29 22:05:55 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017528.html

Subject: FAILED : Bluebream / Python2.5.2 32bit linux
From: ccomb at free.fr
Date: Thu Jul 29 22:06:10 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017529.html

Subject: FAILED : Bluebream / Python2.6.4 32bit linux
From: ccomb at free.fr
Date: Thu Jul 29 22:06:11 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017530.html

Subject: FAILED : winbot / ztk_dev py_244_win32
From: buildbot at winbot.zope.org
Date: Thu Jul 29 22:08:53 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017531.html

Subject: FAILED : winbot / ztk_dev py_254_win32
From: buildbot at winbot.zope.org
Date: Thu Jul 29 22:16:05 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017533.html

Subject: FAILED : winbot / ztk_dev py_265_win32
From: buildbot at winbot.zope.org
Date: Thu Jul 29 22:23:12 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017534.html

Subject: FAILED : winbot / ztk_dev py_265_win64
From: buildbot at winbot.zope.org
Date: Thu Jul 29 22:29:58 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017536.html

Subject: FAILED : winbot / ztk_10 py_244_win32
From: buildbot at winbot.zope.org
Date: Thu Jul 29 22:38:23 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017537.html

Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit
From: ccomb at free.fr
Date: Thu Jul 29 23:45:46 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017541.html

Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit
From: ccomb at free.fr
Date: Thu Jul 29 23:48:33 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017542.html

Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit
From: ccomb at free.fr
Date: Thu Jul 29 23:48:36 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017543.html

Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux
From: ccomb at free.fr
Date: Fri Jul 30 00:45:19 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017546.html

Subject: FAILED : winbot / ZODB_dev py_265_win32
From: buildbot at winbot.zope.org
Date: Fri Jul 30 00:45:45 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017547.html

Subject: FAILED : winbot / ZODB_dev py_270_win32
From: buildbot at winbot.zope.org
Date: Fri Jul 30 02:46:57 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017552.html

Subject: FAILED : winbot / ZODB_dev py_270_win64
From: buildbot at winbot.zope.org
Date: Fri Jul 30 03:41:47 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017553.html

Subject: FAILED : Zope Buildbot / ztk_win slave-win
From: jdriessen at thehealthagency.com
Date: Fri Jul 30 07:20:37 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017557.html

Subject: FAILED : Zope Buildbot / zope2.12 slave-osx
From: jdriessen at thehealthagency.com
Date: Fri Jul 30 07:24:01 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017559.html

Subject: FAILED : Zope Buildbot / zope2 slave-osx
From: jdriessen at thehealthagency.com
Date: Fri Jul 30 07:24:06 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017560.html

Subject: FAILED : Zope Buildbot / ztk slave-osx
From: jdriessen at thehealthagency.com
Date: Fri Jul 30 07:24:10 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017561.html


Unknown
---

Subject: [zodb-tests] buildbot failure in Enfold Systems on 
zodb-trunk-python-2.6-maestro
From: buildbot at enfoldsystems.com
Date: Fri Jul 30 04:00:31 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017554.html


Tests passed OK
---

Subject: OK : Zope 3.4 Known Good Set / py2.4-64bit-linux
From: buildbot at pov.lt
Date: Thu Jul 29 21:08:56 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017520.html

Subject: OK : Zope 3.4 Known Good Set / py2.4-32bit-linux
From: buildbot at pov.lt
Date: Thu Jul 29 21:29:16 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017521.html

Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Thu Jul 29 21:38:32 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017522.html

Subject: OK : Zope-2.11 Python-2.4.6 : Linux
From: Zope Tests
Date: Thu Jul 29 21:40:32 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017523.html

Subject: OK : Zope-2.12 Python-2.6.5 : Linux
From: Zope Tests
Date: Thu Jul 29 21:42:32

Re: [Zope-dev] Class advisors in Python 3

2010-07-30 Thread Hanno Schlichting
On Fri, Jul 30, 2010 at 1:53 PM, Stephan Richter
 wrote:
> On Friday, July 30, 2010, Hanno Schlichting wrote:
>> zope.interface contains 2to3 fixers to rewrite them to a class
>> decorator syntax IIRC.
>
> Wow, that's really nice. BTW, does Python 2.7 support class decorators
> already? If so, we could slowly migrate code to that syntax without having to
> go Py3 all the way.

Class decorators were introduced in Python 2.6.

I think it's going to be a whole before we can require 2.6 as a minimum version.

Hanno
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Class advisors in Python 3

2010-07-30 Thread Stephan Richter
On Friday, July 30, 2010, Hanno Schlichting wrote:
> zope.interface contains 2to3 fixers to rewrite them to a class
> decorator syntax IIRC.

Wow, that's really nice. BTW, does Python 2.7 support class decorators 
already? If so, we could slowly migrate code to that syntax without having to 
go Py3 all the way.

Regards,
Stephan
-- 
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Class advisors in Python 3

2010-07-30 Thread Hanno Schlichting
On Fri, Jul 30, 2010 at 1:31 PM, Baiju M  wrote:
> Does class advisors like 'implements' and 'adapts' are going to work
> in Python 3 ? If not, should we discourage its usage now ?

They won't work anymore.

zope.interface contains 2to3 fixers to rewrite them to a class
decorator syntax IIRC.

Hanno
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Class advisors in Python 3

2010-07-30 Thread Wichert Akkerman
On 7/30/10 13:31 , Baiju M wrote:
> Hi,
>
> Does class advisors like 'implements' and 'adapts' are going to work
> in Python 3 ? If not, should we discourage its usage now ?

Regardless if they work or not I would love to have a decorator version 
of them.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Class advisors in Python 3

2010-07-30 Thread Baiju M
Hi,

Does class advisors like 'implements' and 'adapts' are going to work
in Python 3 ? If not, should we discourage its usage now ?

Regards,
Baiju M
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] unit test policy questions

2010-07-30 Thread yuppie
Hi!


Marius Gedminas wrote:
>> And if I use the -t option (-ttest_tool), most tests fail :(
>
> That is an indication that the tests aren't independent.  I would
> consider such a test suite to be broken.

Well. In this case the tests are independent from each other, but not 
from the way tests are filtered:

The -m filter is applied *before* test modules are imported.

The -t filter is applied *after* importing all available test modules.

Some nasty code in Zope 2 behaves differently if different modules are 
imported before running the tests.


Cheers,

Yuppie
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )