On Fri, Feb 25, 2011 at 12:05, Laurence Rowe l...@lrowe.co.uk wrote:
I take that back, that documentation is incorrect, they have indeed
stopped working.
You are allowed to catch them, but not raise them. This is so you can
have code that runs on old Pythons with old libraries still.
But in
Hi,
I find a few string exceptions leftover in Zope 2.13 code.
However, they are not allowed anymore in Python 2.6.
I guess that the remaining string exceptions are in dead/semidead code.
What practice has been followed until now regarding fixing those
exceptions ?
Regards
--
Godefroid
Hi.
On Fri, Feb 25, 2011 at 11:58 AM, Godefroid Chapelle
got...@bubblenet.be wrote:
I find a few string exceptions leftover in Zope 2.13 code.
What practice has been followed until now regarding fixing those
exceptions ?
Just upgrade them to new-style exception classes. Since string
On 25 February 2011 10:58, Godefroid Chapelle got...@bubblenet.be wrote:
Hi,
I find a few string exceptions leftover in Zope 2.13 code.
However, they are not allowed anymore in Python 2.6.
I guess that the remaining string exceptions are in dead/semidead code.
What practice has been
On 25 February 2011 11:03, Laurence Rowe l...@lrowe.co.uk wrote:
On 25 February 2011 10:58, Godefroid Chapelle got...@bubblenet.be wrote:
Hi,
I find a few string exceptions leftover in Zope 2.13 code.
However, they are not allowed anymore in Python 2.6.
I guess that the remaining string
Le 25/02/11 12:03, Laurence Rowe a écrit :
On 25 February 2011 10:58, Godefroid Chapellegot...@bubblenet.be wrote:
Hi,
I find a few string exceptions leftover in Zope 2.13 code.
However, they are not allowed anymore in Python 2.6.
I guess that the remaining string exceptions are in
Le 25/02/11 12:03, Hanno Schlichting a écrit :
I find a few string exceptions leftover in Zope 2.13 code.
What practice has been followed until now regarding fixing those
exceptions ?
Just upgrade them to new-style exception classes. Since string
exceptions cannot possibly work anymore,
On 25 February 2011 11:09, Godefroid Chapelle got...@bubblenet.be wrote:
Le 25/02/11 12:03, Laurence Rowe a écrit :
On 25 February 2011 10:58, Godefroid Chapellegot...@bubblenet.be wrote:
Hi,
I find a few string exceptions leftover in Zope 2.13 code.
However, they are not allowed anymore
On 25 February 2011 11:14, Godefroid Chapelle got...@bubblenet.be wrote:
Le 25/02/11 12:03, Hanno Schlichting a écrit :
I find a few string exceptions leftover in Zope 2.13 code.
What practice has been followed until now regarding fixing those
exceptions ?
Just upgrade them to new-style
On Fri, Feb 25, 2011 at 12:14 PM, Godefroid Chapelle
got...@bubblenet.be wrote:
Where should those fixes happen ?
2.13 branch and trunk I suppose
+1 - if you really feel like it you could backport to 2.12 branch as
well (as it only supports Python 2.6 too).
Hanno
Am 25.02.2011, 12:26 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
+1 - if you really feel like it you could backport to 2.12 branch as
well (as it only supports Python 2.6 too).
- 1 against backporting unless you are experiencing the errors on a 2.12
based system.
Charlie
--
Charlie
On Fri, Feb 25, 2011 at 12:32 PM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
Am 25.02.2011, 12:26 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
+1 - if you really feel like it you could backport to 2.12 branch as
well (as it only supports Python 2.6 too).
- 1 against
On Feb 25, 2011, at 6:38 AM, Hanno Schlichting wrote:
On Fri, Feb 25, 2011 at 12:32 PM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
Am 25.02.2011, 12:26 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
+1 - if you really feel like it you could backport to 2.12 branch as
well (as
13 matches
Mail list logo
