Message194612
| Author | pitrou |
|---|---|
| Recipients | Arfrever, Robin.Schreiber, asvetlov, effbot, eli.bendersky, pitrou |
| Date | 2013-08-07.14:00:07 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1399729306.48655520.1375884001005.JavaMail.root@zimbra10-e2.priv.proxad.net> |
| In-reply-to | <CAF-Rda9PFepvu4VY1Ux_xZnbyhzevoMAoqoGfv-LSU_jQphq2g@mail.gmail.com> |
| Content | |
|---|---|
> That's true, but I thought one of the goals of PEP 3121 is to > separate > states between sub-interpreters. So that one can't corrupt another. > I'm not > sure how much it matters in practice in this case of the pyexpat > capsule; > need to look into it more. pyexpat's "capi" object is a static struct inside pyexpat.c, so that wouldn't change anything. Separating states between sub-interpreters only matters when said state is mutable, which it isn't here. > I don't see a call to PyState_AddModule. What am I missing? It is called implicitly when an extension module is imported. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-07 14:00:07 | pitrou | set | recipients: + pitrou, effbot, Arfrever, eli.bendersky, asvetlov, Robin.Schreiber |
| 2013-08-07 14:00:07 | pitrou | link | issue15651 messages |
| 2013-08-07 14:00:07 | pitrou | create | |