Message394374
| Author | trygveaa |
|---|---|
| Recipients | corona10, eric.snow, erlendaasland, lukasz.langa, shihai1991, trygveaa, vstinner |
| Date | 2021-05-25.16:14:13 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1621959253.7.0.161300783852.issue44050@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> The _PyImport_FixupExtensionObject() change impacts extensions using the legacy API and so should not be used in subinterpreters. I'm not using that directly in my code, but I guess it's used indirectly? If it shouldn't be used, what's the alternative in 3.9? > Maybe the old behavior was better: if an extension uses the old API, share its state between all interpreters. Since this worked fine as far as I know before 3.9, and currently breaks existing applications, this is probably better yes. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2021-05-25 16:14:13 | trygveaa | set | recipients: + trygveaa, vstinner, lukasz.langa, eric.snow, corona10, shihai1991, erlendaasland |
| 2021-05-25 16:14:13 | trygveaa | set | messageid: <1621959253.7.0.161300783852.issue44050@roundup.psfhosted.org> |
| 2021-05-25 16:14:13 | trygveaa | link | issue44050 messages |
| 2021-05-25 16:14:13 | trygveaa | create | |