Message364102
| Author |
vstinner |
| Recipients |
fabioz, vstinner |
| Date |
2020年03月13日.15:50:26 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1584114627.25.0.49124699242.issue35370@roundup.psfhosted.org> |
| In-reply-to |
| Content |
Fabio: I added _PyEval_SetProfile() and _PyEval_SetTrace() which take a tstate parameter. These functions have a constraint: the caller must hold the GIL. Is it an acceptable constraint for you?
That's not something new, it's already the code in Python 3.8, it's just that it wasn't documented. In Python 3.7, it was less important: Python 3.8 added a call to PySys_Audit() which can execute arbitrary Python code.
Anyway, touching Python internals without holding the GIL is risky: see bpo-1021318 for example. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2020年03月13日 15:50:27 | vstinner | set | recipients:
+ vstinner, fabioz |
| 2020年03月13日 15:50:27 | vstinner | set | messageid: <1584114627.25.0.49124699242.issue35370@roundup.psfhosted.org> |
| 2020年03月13日 15:50:27 | vstinner | link | issue35370 messages |
| 2020年03月13日 15:50:27 | vstinner | create |
|