Sorry about introducing this. Where can I subscribe to these automated
emails. Also, how do I go about running this locally? On default I tried
running
`./python -m test -l test_capi` did not print anything about leaks. I think
that
using `object.__new__` as a decorator here is the same as
Raymond Hettinger writes:
> Thanks for hunting this down. I had seen the automated reference leak
> posts but didn't suspect that a pure python class would have caused
> the leak.
>
> I'm re-opening
>
On Wed, Oct 21, 2015 at 9:32 AM, Raymond Hettinger
wrote:
> I'm re-opening
> https://mail.python.org/pipermail/python-dev/2015-October/141993.html
Presumably you meant http://bugs.python.org/issue24379. :)
-eric
___
Le 21/10/2015 17:32, Raymond Hettinger a écrit :
>
> Thanks for hunting this down. I had seen the automated reference leak posts
> but didn't suspect that a pure python class would have caused the leak.
Yes, it's a bit baffling at first.
> I'm re-opening
>
> On Oct 20, 2015, at 3:57 PM, Antoine Pitrou wrote:
>
>
>> These leaks have been here a while. Anyone know the cause?
>>
>> On Tue, 20 Oct 2015 at 01:47 wrote:
>>
>>> results for d7e490db8d54 on branch "default"
>>>
>>>
>>>
On Wed, 21 Oct 2015 at 09:33 Joe Jevnik wrote:
> Sorry about introducing this. Where can I subscribe to these automated
> emails.
>
The emails are sent to the python-checkins mailing list.
> Also, how do I go about running this locally?
>
If you look at the bottom of
On 10/21/2015 08:53 AM, Random832 wrote:
If a pure python class can cause a reference leak, doesn't that mean it
is only a symptom rather than the real cause? Or is it that the use of
@object.__new__ is considered "too clever" to be worth fixing?
Where can I find out more about using
On Wed, Oct 21, 2015 at 10:10:56AM -0700, Ethan Furman wrote:
> On 10/21/2015 08:53 AM, Random832 wrote:
>
> >If a pure python class can cause a reference leak, doesn't that mean it
> >is only a symptom rather than the real cause? Or is it that the use of
> >@object.__new__ is considered "too
These leaks have been here a while. Anyone know the cause?
On Tue, 20 Oct 2015 at 01:47 wrote:
> results for d7e490db8d54 on branch "default"
>
>
> test_capi leaked [5411, 5411, 5411] references, sum=16233
> test_capi leaked
> These leaks have been here a while. Anyone know the cause?
>
> On Tue, 20 Oct 2015 at 01:47 wrote:
>
>> results for d7e490db8d54 on branch "default"
>>
>>
>> test_capi leaked [5411, 5411, 5411] references, sum=16233
>> test_capi leaked [1421,
[Adding Raymond to the thread, since he doesn't always follow the lists
closely.]
On Tue, Oct 20, 2015 at 8:23 PM, Benjamin Peterson
wrote:
>
>
> On Tue, Oct 20, 2015, at 15:57, Antoine Pitrou wrote:
> >
> > > These leaks have been here a while. Anyone know the cause?
> > >
On Tue, Oct 20, 2015, at 15:57, Antoine Pitrou wrote:
>
> > These leaks have been here a while. Anyone know the cause?
> >
> > On Tue, 20 Oct 2015 at 01:47 wrote:
> >
> >> results for d7e490db8d54 on branch "default"
> >>
> >>
> >> test_capi
12 matches
Mail list logo