This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | vstinner |
|---|---|
| Recipients | docs@python, eric.snow, ncoghlan, vstinner |
| Date | 2017年11月24日.13:19:15 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1511529556.02.0.213398074469.issue32124@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Follow-up of bpo-32086, bpo-32096 and "[Python-Dev] Python initialization and embedded Python" thread: https://mail.python.org/pipermail/python-dev/2017-November/150605.html I propose to explicitly list functions that can be safetely called before Py_Initialize(). This safety warranty must be part of the C API. Maybe we should even test all tests function in test_capi using Programs/_testembed, as we did for Py_DecodeLocale() and Py_SetProgramName() in commit 9e87e7776f7ace66baaf7247233afdabd00c2b44 ("pre_initialization_api" test). Attached PR adds proposed documentation. It also documents "global configuration variables" like Py_DebugFlag. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017年11月24日 13:19:16 | vstinner | set | recipients: + vstinner, ncoghlan, docs@python, eric.snow |
| 2017年11月24日 13:19:16 | vstinner | set | messageid: <1511529556.02.0.213398074469.issue32124@psf.upfronthosting.co.za> |
| 2017年11月24日 13:19:15 | vstinner | link | issue32124 messages |
| 2017年11月24日 13:19:15 | vstinner | create | |