On Thu, Apr 29, 2010 at 21:55, Tres Seaver wrote:
> +1. Does zope.testing depend on zope.testrunner already?
No, and with this zope.testrunner doesn't have to depend on
zope.testing either, except for running the tests. Freedom baby yeah!
:)
--
Lennart Regebro: Python, Zope, Plone, Grok
http:/
On Thu, Apr 29, 2010 at 22:03, Hanno Schlichting wrote:
> On Thu, Apr 29, 2010 at 10:00 PM, Lennart Regebro wrote:
>> OK, I started carefully with zope.interface 3.6.0. :)
>>
>> Source only so far. I have a Windows machine, and I could make Windows
>> releases as well, I guess. Is there any docs
On Thu, Apr 29, 2010 at 10:00 PM, Lennart Regebro wrote:
> OK, I started carefully with zope.interface 3.6.0. :)
>
> Source only so far. I have a Windows machine, and I could make Windows
> releases as well, I guess. Is there any docs on what's needed for
> that? I haven't built python extensions
OK, I started carefully with zope.interface 3.6.0. :)
Source only so far. I have a Windows machine, and I could make Windows
releases as well, I guess. Is there any docs on what's needed for
that? I haven't built python extensions on Windows since 2004. :)
--
Lennart Regebro: Python, Zope, Plone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
> There is a zope.testing.exceptions module. It contains only one
> exception: DocTestFailureException, which is used by the testrunner,
> and as far as I can tell, only the testrunner. So we should probably
> move that one over
There is a zope.testing.exceptions module. It contains only one
exception: DocTestFailureException, which is used by the testrunner,
and as far as I can tell, only the testrunner. So we should probably
move that one over to zope.testrunner as well. Which means deprecating
it in zope.testing, of cou
On Thu, Apr 29, 2010 at 18:51, Tres Seaver wrote:
> Never mind, I figured it out.
OK, thanks!
--
Lennart Regebro: http://regebro.wordpress.com/
Python 3 Porting: http://python-incompatibility.googlecode.com/
+33 661 58 14 64
___
Zope-Dev maillist -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
> Lennart Regebro wrote:
>> I would like to have the following packages released, or the
>> permissions to release them myself. This is all in preparation for
>> Python 3 support.
>
>> zope.interface
>> zope.events
>> zope.exception
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
> I would like to have the following packages released, or the
> permissions to release them myself. This is all in preparation for
> Python 3 support.
>
> zope.interface
> zope.events
> zope.exceptions
> zope.testing
> zc.recip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
> The workflow I am proposing is that when the nightly tests begin to
> break due to a dependeny, the developer updates the setup.py (*NOT* the
> buildout.cfg) to pin minimum or maximum versions of dependencies.
> Later, the develop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam GROSZER wrote:
> Hello Tres,
>
> Thursday, April 29, 2010, 4:05:36 PM, you wrote:
>
> TS> Stephan Richter wrote:
>>> On Thursday 29 April 2010, Baiju M wrote:
> +1 to use a KGS. ZTK or BB depending on what the dependencies are.
Since no
Hello Stephan,
Thursday, April 29, 2010, 3:45:13 PM, you wrote:
SR> On Thursday 29 April 2010, Baiju M wrote:
>> > I did a few releases just using mingw32. I think it is the best we can do
>> > for now that scales. As for Python versions, you simply have to
>> > installthem all and go through th
Tres Seaver a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Zope Tests Summarizer wrote:
>
>> Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit
>> From: ccomb at free.fr
>> Date: Wed Apr 28 23:00:24 EDT 2010
>> URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014174.
I would like to have the following packages released, or the
permissions to release them myself. This is all in preparation for
Python 3 support.
zope.interface
zope.events
zope.exceptions
zope.testing
zc.recipe.testrunner
The releases of zope.interface, zope.events and zope.exceptions
introduce
Hello Tres,
Thursday, April 29, 2010, 4:05:36 PM, you wrote:
TS> Stephan Richter wrote:
>> On Thursday 29 April 2010, Baiju M wrote:
+1 to use a KGS. ZTK or BB depending on what the dependencies are.
>>> Since normally we don't pin versions in trunk, I guess we need to
>>> do the pinning in
On Thu, Apr 29, 2010 at 9:46 AM, Stephan Richter
wrote:
> On Thursday 29 April 2010, Baiju M wrote:
>> > +1 to use a KGS. ZTK or BB depending on what the dependencies are.
>>
>> Since normally we don't pin versions in trunk, I guess we need to
>> do the pinning in maintenance branches. Otherwise
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephan Richter wrote:
> On Thursday 29 April 2010, Baiju M wrote:
>>> +1 to use a KGS. ZTK or BB depending on what the dependencies are.
>> Since normally we don't pin versions in trunk, I guess we need to
>> do the pinning in maintenance branches. O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zope Tests Summarizer wrote:
> Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit
> From: ccomb at free.fr
> Date: Wed Apr 28 23:00:24 EDT 2010
> URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014174.html
>
> Subject: FAILED : ZTK 1.0d
On Thursday 29 April 2010, Baiju M wrote:
> > +1 to use a KGS. ZTK or BB depending on what the dependencies are.
>
> Since normally we don't pin versions in trunk, I guess we need to
> do the pinning in maintenance branches. Otherwise we can
> keep the version pinning in trunk, but comment the "v
On Thursday 29 April 2010, Baiju M wrote:
> > I did a few releases just using mingw32. I think it is the best we can do
> > for now that scales. As for Python versions, you simply have to
> > installthem all and go through the dance.
>
> Does mingw32 works for 64 bit also ?
If you can isntall it
On Thu, Apr 29, 2010 at 6:36 PM, Stephan Richter
wrote:
> On Wednesday 28 April 2010, Adam GROSZER wrote:
>> How do you used to build binaries for windowze?
>> I mean which compilers do you use? mingw32? MS?
>> Ohhh and don't forget win64 ;-)
>> and various python version, like from 2.4 up to 3.1.
On Thu, Apr 29, 2010 at 6:31 PM, Stephan Richter
wrote:
> On Thursday 29 April 2010, Adam GROSZER wrote:
>> I'd say we should nail the package versions on (at least) tags.
>> Either to a KGS, or drop a versions.cfg into the package.
>> The recipe buildout.dumppickedversions would be handy.
>
> +1
On Wednesday 28 April 2010, Adam GROSZER wrote:
> How do you used to build binaries for windowze?
> I mean which compilers do you use? mingw32? MS?
> Ohhh and don't forget win64 ;-)
> and various python version, like from 2.4 up to 3.1.
I did a few releases just using mingw32. I think it is the be
On Thursday 29 April 2010, Adam GROSZER wrote:
> I'd say we should nail the package versions on (at least) tags.
> Either to a KGS, or drop a versions.cfg into the package.
> The recipe buildout.dumppickedversions would be handy.
+1 to use a KGS. ZTK or BB depending on what the dependencies are.
Summary of messages to the zope-tests list.
Period Wed Apr 28 12:00:00 2010 UTC to Thu Apr 29 12:00:00 2010 UTC.
There were 16 messages: 6 from Zope Tests, 9 from ccomb at free.fr, 1 from ct
at gocept.com.
Test failures
-
Subject: FAILED: Repository policy check found errors in 670
Hello,
I found while trying to get the KGS 3.4.1 together that MISSING
versions on tags/previous versions are BAD.
The problem is that if you work with the trunk you test the package
against (usually) the current versions.
If you later get back to a package for a bugfix or whatever, it's a
pain t
26 matches
Mail list logo
