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 | Rhamphoryncus |
|---|---|
| Recipients | Rhamphoryncus |
| Date | 2008年06月13日.04:55:17 |
| SpamBayes Score | 0.1301843 |
| Marked as misclassified | No |
| Message-id | <1213332926.11.0.960105812528.issue3100@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Specific enough yet? Seems the WeakValueDictionary and the module clearing aren't necessary. A subclass of weakref is created. The target of this weakref is added as an attribute of the weakref. So long as a callback is present there will be a crash on shutdown. However, if the callback prints the attribute, you get a crash right then. The weakref claims to be dead, which shouldn't be possible when the weakref's attributes have a strong reference to the target. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月13日 04:55:28 | Rhamphoryncus | set | spambayes_score: 0.130184 -> 0.1301843 recipients: + Rhamphoryncus |
| 2008年06月13日 04:55:26 | Rhamphoryncus | set | spambayes_score: 0.130184 -> 0.130184 messageid: <1213332926.11.0.960105812528.issue3100@psf.upfronthosting.co.za> |
| 2008年06月13日 04:55:24 | Rhamphoryncus | link | issue3100 messages |
| 2008年06月13日 04:55:24 | Rhamphoryncus | create | |