On Wednesday, 27 February 2019 15:11:31 GMT Jean-Paul Calderone wrote:
> On Wed, Feb 27, 2019 at 10:07 AM Scott, Barry
>
> wrote:
> > The code I have posted is the good version so it works and the assert
> > does not fire. My goal is to show what I assume is the correct way to code
> > a function
Is it intentional to trigger this message?
The reason I ask it it comes from defer.py DebugInfo.___del__().
I though that DebugInfo objects are only created
if defer.DebugInfo.debug == True.
But in Deferred._runCallbacks:701 its created without a check in the
debug flag.
The reason I have notice