Message91993
| Author | jmalicki |
|---|---|
| Recipients | eggy, georg.brandl, jmalicki, r.david.murray |
| Date | 2009-08-27.02:17:31 |
| SpamBayes Score | 2.3516506e-08 |
| Marked as misclassified | No |
| Message-id | <1251339453.42.0.0596362079559.issue4684@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Is it actually just documentation? Before Python 2.5, things worked according to the documentation, and nothing in the revisions that changed the behavior suggested this change in behavior was intentional. Moving the WaitForThreadShutdown() from Modules/main.c to Py_Finalize() would also fix this problem - I wonder why that wasn't the original change, as it more closely mirrors how Python 2.4 worked, and the documentation suggests? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-08-27 02:17:33 | jmalicki | set | recipients: + jmalicki, georg.brandl, eggy, r.david.murray |
| 2009-08-27 02:17:33 | jmalicki | set | messageid: <1251339453.42.0.0596362079559.issue4684@psf.upfronthosting.co.za> |
| 2009-08-27 02:17:32 | jmalicki | link | issue4684 messages |
| 2009-08-27 02:17:31 | jmalicki | create | |