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 |
|