On 16.04.2012 08:31, Philipp Kern wrote:
Is there anything incompatible when going from 2.6 to 2.7? Because it does
mean that you need to change all scripts in lockstep with the distro upgrade,
because 2.7 is not in squeeze and 2.6 is not in wheezy, unless(!) python2.6
from squeeze is still inst
On Sun, Apr 15, 2012 at 08:26:33PM +0200, Matthias Klose wrote:
> On 15.04.2012 12:46, Mehdi Dogguy wrote:
> >On 04/14/2012 07:39 PM, Matthias Klose wrote:
> >>I would like to remove python2.6 for the wheezy release
> >Since python2.6 was the default python interpreter in Squeeze, shouldn't
> >we k
On 15.04.2012 12:46, Mehdi Dogguy wrote:
On 04/14/2012 07:39 PM, Matthias Klose wrote:
I would like to remove python2.6 for the wheezy release
Since python2.6 was the default python interpreter in Squeeze, shouldn't
we keep it in Wheezy and remove it from Wheezy+1? (as we did with python2.5)
On 04/14/2012 07:39 PM, Matthias Klose wrote:
>
> I would like to remove python2.6 for the wheezy release
Since python2.6 was the default python interpreter in Squeeze, shouldn't
we keep it in Wheezy and remove it from Wheezy+1? (as we did with python2.5)
Regards,
--
Mehdi Dogguy مهدي الدڤي
ht
On Sat, Apr 14, 2012 at 19:39:59 +0200, Matthias Klose wrote:
> ("We intend to provide source-only security fixes for the Python 2.6
> series until October 2013 (five years after the 2.6 final
> release)").
>
Does that matter, considering we're currently not fixing python security
bugs in stable
Zope2 maintainers,
The only application in wheezy which doesn't work with python2.7 is zope2.12.
Zope2.13 was released in 2010, but not yet packaged. The rationale for this is
that the probably most popular zope2 application plone is not yet updated for
zope2.13 (but plone itself is not avail
6 matches
Mail list logo
