Message408012
| Author | vstinner |
|---|---|
| Recipients | corona10, eric.snow, erlendaasland, methane, serhiy.storchaka, vstinner |
| Date | 2021-12-08.11:36:16 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1638963377.09.0.36333009744.issue46006@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> Should `_PyUnicode_EqualToASCIIId()` support comparing two unicode from different interpreter? Right now, there still many cases where objects are still shared between two interpreters: * None, True, False singletons * strings from code objects (according to what I saw when I reproduced the issue) * objects from static types: type name (str), subtypes (tuple), MRO (tuple), etc. * etc. More details in the following issues: * bpo-40533: [subinterpreters] Don't share Python objects between interpreters * bpo-40512: [subinterpreters] Meta issue: per-interpreter GIL |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2021-12-08 11:36:17 | vstinner | set | recipients: + vstinner, methane, eric.snow, serhiy.storchaka, corona10, erlendaasland |
| 2021-12-08 11:36:17 | vstinner | set | messageid: <1638963377.09.0.36333009744.issue46006@roundup.psfhosted.org> |
| 2021-12-08 11:36:17 | vstinner | link | issue46006 messages |
| 2021-12-08 11:36:16 | vstinner | create | |