Martin v. Löwis wrote:
> when some caller of PyEval_EvalFrameEx still carries
> a pointer to some object that got deleted, and then still some code can
> get hold of the then-deleted object.
I seem to have missed the beginning of this discussion.
I don't see what the problem is here. If a caller n
Jeffrey Yasskin wrote:
> On Feb 16, 2008 3:12 PM, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
>> Should we however intensively search and correct all of them?
>> Is there a clever way to prevent these problems globally, for example
>> by delaying finalizers "just a little"?
>
> A simple way to
On Feb 17, 2:42 pm, "Raymond Hettinger" <[EMAIL PROTECTED]> wrote:
> There are some modules like Decimal that make a promise to run on earlier
> versions of Python. In those cases only the first change (backwards
> compatible)
> should be made. Our 5,000 line Decimal package will need to wait fo
On Feb 17, 2008 2:42 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> There are some modules like Decimal that make a promise to run on earlier
> versions of Python. In those cases only the first change (backwards
> compatible)
> should be made. Our 5,000 line Decimal package will need to wait
[Christian Heimes]
> I like to run the 2to3 tool with raise and except fixers over the 2.6
> sources. The raise fixer changes "raise Exception, msg" to "raise
> Exception(msg)" and the except fixer replaces "except Exception, err" by
> "except Exception as err".
+1 The new syntax so much better t
Christian Heimes schrieb:
> Good evening everybody!
>
> I like to run the 2to3 tool with raise and except fixers over the 2.6
> sources. The raise fixer changes "raise Exception, msg" to "raise
> Exception(msg)" and the except fixer replaces "except Exception, err" by
> "except Exception as err".
On Feb 16, 2008 3:12 PM, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
> Should we however intensively search and correct all of them?
> Is there a clever way to prevent these problems globally, for example
> by delaying finalizers "just a little"?
A simple way to do this would be to push object
Aargh. Extra long lines again. Here's a repost.
An update: after some discussion, we're planning a PEP for the "with
ieee754"
and related ideas, perhaps aimed at Python 3.1; there are lots of difficult
decisions to be made, and plenty that would benefit from community feedback.
In the meantim
Sounds good to me. Along those lines, shall we work on fixing warnings
that -3 raises in the regression test suite?
On Feb 17, 2008 8:57 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Good evening everybody!
>
> I like to run the 2to3 tool with raise and except fixers over the 2.6
> sources. Th
An update: after some discussion, we're planning a PEP for the "with
ieee754" and related ideas, perhaps aimed at Python 3.1; there are lots of
difficult decisions to be made, and plenty that would benefit from community
feedback. In the meantime, we'll get the rest of the fixes/additions tidied
Good evening everybody!
I like to run the 2to3 tool with raise and except fixers over the 2.6
sources. The raise fixer changes "raise Exception, msg" to "raise
Exception(msg)" and the except fixer replaces "except Exception, err" by
"except Exception as err". In my humble opinion the Python stdlib
* Eric Smith wrote:
> André Malo wrote:
> > I guess, a clean and complete solution (besides re-implementing the
> > whole thing) would be to resolve each single format character with
> > strftime, decode according to the locale and re-assemble the result
> > string piece by piece. Doh!
>
> That's
12 matches
Mail list logo
