continuous integration/testing for python packages [Was: Is it worth back porting PEP 3147...]

2010-04-27 Thread Nicolas Chauvat
Hi, [discussion started at http://lists.debian.org/debian-python/2010/04/msg00046 should we continue or trim some of the cc'ed lists ?] On Mon, Apr 26, 2010 at 06:41:16PM -0400, Barry Warsaw wrote: > On Apr 26, 2010, at 06:35 PM, Nicolas Chauvat wrote: > >On Thu, Apr 22, 2010 at 01:52:11PM -0400,

Python2.4 has been removed, now what for Zopistas and Plonistas?

2010-04-27 Thread Toni Mueller
Hi, unfortunately, I've missed decision to remove Python2.4 from Debian, but the result is that Zope2.10, required for Plone 3.x, will not run on Squeeze anymore, and that the zope2.10 package from sid is now completely uninstallable. Even installing Zope from upstream's source, imho "the" recom

Re: Python2.4 has been removed, now what for Zopistas and Plonistas?

2010-04-27 Thread Luca Falavigna
Il 27/04/2010 11.17, Toni Mueller ha scritto: > I am not sure that this was a good choice, although I feel the pain of > maintaining a Python 2.4 stack in Squeeze, because: > > * Plone, and thus Zope is still a major Python application, and I >heavily doubt that Plone 4.0 will see the light i

Re: Python2.4 has been removed, now what for Zopistas and Plonistas?

2010-04-27 Thread Fabio Tranchitella
* 2010-04-27 15:16, Luca Falavigna wrote: > When dealing with python2.4 removal, we asked Fabio about state of the > art of Zope 2.14 and Plone 4. He replied he hadn't way to look at them at > that time, and he would have looked upgrading the whole stack in > April/May. CCing him, to see if things

Re: continuous integration/testing for python packages [Was: Is it worth back porting PEP 3147...]

2010-04-27 Thread Barry Warsaw
On Apr 27, 2010, at 10:01 AM, Nicolas Chauvat wrote: >[discussion started at >http://lists.debian.org/debian-python/2010/04/msg00046 >should we continue or trim some of the cc'ed lists ?] Is there a better place to discuss Python packaging issues that are of interest to both Debian and Ubuntu? A

Re: Python2.4 has been removed, now what for Zopistas and Plonistas?

2010-04-27 Thread Toni Mueller
Hi, On Tue, 27.04.2010 at 15:42:45 +0200, Fabio Tranchitella wrote: > The current stable release of Plone requires python2.4 and Zope2.10, which > we cannot support in squeeze. I see no way to really support them, so I'd > prefer to have the packages removed. from my point of view, only Python

Re: Python2.4 has been removed, now what for Zopistas and Plonistas? [ADDENDUM]

2010-04-27 Thread Toni Mueller
Hi, I forgot to ask what'd be the best way to go forward for Plonistas? I really think that there should be some time for Plonistas to upgrade, which the current scheme does not allow for. I see the following options: * Compile everything from source, including Python 2.4 So far, Debian's P

Re: Python2.4 has been removed, now what for Zopistas and Plonistas? [ADDENDUM]

2010-04-27 Thread Barry Warsaw
On Apr 27, 2010, at 06:32 PM, Toni Mueller wrote: >I'm not sure about how much the changes in the infrastructure would be >an obstacle, or prevent this from happening (didn't check yet), and I >don'tknow how the group thinks about the political and/or personal >issues involved, either. What I do s

Re: Python2.4 has been removed, now what for Zopistas and Plonistas? [ADDENDUM]

2010-04-27 Thread Fabio Tranchitella
* 2010-04-27 18:33, Toni Mueller wrote: > I forgot to ask what'd be the best way to go forward for Plonistas? > I really think that there should be some time for Plonistas to upgrade, > which the current scheme does not allow for. I personally use the unified installer, and it works fine; I liked

Re: continuous integration/testing for python packages [Was: Is it worth back porting PEP 3147...]

2010-04-27 Thread Nicolas Chauvat
On Tue, Apr 27, 2010 at 11:07:51AM -0400, Barry Warsaw wrote: > On Apr 27, 2010, at 10:01 AM, Nicolas Chauvat wrote: > There's also buildbot of course, which I guess it the granddad of Python CI > tools, kind of. Yes, buildbot is the old-timer and has loads of features. As far as I know, extractin