Message153945
| Author | tarek |
|---|---|
| Recipients | grahamd, neologix, pitrou, tarek |
| Date | 2012-02-22.09:45:21 |
| SpamBayes Score | 0.0011003043 |
| Marked as misclassified | No |
| Message-id | <1329903922.15.0.438710745063.issue14073@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Add an actual example here at least of how with the proposed feature your code would then look.
That's the part I am not sure at all about in fact. I don't know at all the internals in the shutdown process in Python and I was hoping Antoine would give us a proposal here.
I would suspect simply adding to the base thread class an .atexit() method that's called when atexit() is called, would do the trick since we'd be able to do things like:
def atexit(self):
... do whatever cleanup needed...
self.join()
but I have no real experience in these internals. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-02-22 09:45:22 | tarek | set | recipients: + tarek, pitrou, grahamd, neologix |
| 2012-02-22 09:45:22 | tarek | set | messageid: <1329903922.15.0.438710745063.issue14073@psf.upfronthosting.co.za> |
| 2012-02-22 09:45:21 | tarek | link | issue14073 messages |
| 2012-02-22 09:45:21 | tarek | create | |