Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Make sure that when we invoke callback functions associated with weak | Fred Drake | 2001-12-10 | 1 | -20/+24 |
| | | | | | | references, we do not allow any outstanding exceptions "leak" into the callback's execution state. This closes SF bug #478534. | ||||
* | weakref_repr(), proxy_repr(): Conversion of sprintf() to | Barry Warsaw | 2001-11-28 | 1 | -8/+11 |
| | | | | PyOS_snprintf() for buffer overrun avoidance. | ||||
* | Fixes for possible buffer overflows in sprintf() usages. | Marc-André Lemburg | 2001-11-28 | 1 | -1/+1 |
| | |||||
* | Referencable is not a word, so don't use it in an error message <wink>. | Jeremy Hylton | 2001-10-22 | 1 | -2/+2 |
| | |||||
* | Remove an unnecessary check for NULL. | Fred Drake | 2001-10-18 | 1 | -4/+3 |
| | |||||
* | When weakref proxies are involved in binary & ternary slot operations, | Fred Drake | 2001-10-18 | 1 | -15/+28 |
| | | | | | | | | | | | the left-hand operand may not be the proxy in all cases. If it isn't, we end up doing two things: a) unwrapping something that isn't a PyWeakReference (later resulting in a core dump) and b) passing a proxy as the right-hand operand anyway, even though that can't be handled by the actual handler (maybe eventually causing a core dump). This is fixed by always unwrapping all the proxies involved before passing anything to the actual handler. | ||||
* | The weak reference implementation, separated from the weakref module. | Fred Drake | 2001-10-05 | 1 | -0/+715 |