➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients asvetlov, gvanrossum, methane, ned.deily, python-dev, socketpair, vstinner, yselivanov
Date 2016-11-03.22:26:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJ+EOq+bYe2PzHS-o4tN8i15T74upEACqWZ5KBZRsvNM2Q@mail.gmail.com>
In-reply-to <1478211170.28.0.645416180274.issue28600@psf.upfronthosting.co.za>
Content 
PS. I noticed there are a few lines different between the "upstream" repo
and the 3.5 stdlib:

+            # Wake up the loop if the finalizer was called from
+            # a different thread.
+            self._write_to_self()

On Thu, Nov 3, 2016 at 3:12 PM, Yury Selivanov <report@bugs.python.org>
wrote:

>
> Changes by Yury Selivanov <yselivanov@gmail.com>:
>
>
> ----------
> resolution:  -> fixed
> stage: commit review -> resolved
> status: open -> closed
> type:  -> performance
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue28600>
> _______________________________________
>
History
Date User Action Args
2016-11-03 22:26:39gvanrossumsetrecipients: + gvanrossum, vstinner, ned.deily, asvetlov, methane, socketpair, python-dev, yselivanov
2016-11-03 22:26:39gvanrossumlinkissue28600 messages
2016-11-03 22:26:39gvanrossumcreate