bpo-43322: Use consistent '#include' syntax in extn. tutorial#24851
bpo-43322: Use consistent '#include' syntax in extn. tutorial#24851matthewhughes934 wants to merge 1 commit into
Conversation
Use the same format for Python header files
|
vstinner:urllib_basic_auth_regexLib/urllib/request.pyvstinner:urllib_basic_auth_regexexport http_proxy=http://alice.example.com:8080JunyiXie:fix/pymalloc_subinterpretervstinner:urllib_basic_auth_regexexport http_proxy=http://alice.example.com:8080 |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
|
There is a difference in C between these two formats. Are you suggesting this just for consistency or because you think the example is currently incorrect? |
Sorry, something went wrong.
Purely for consistency. From what I understand the quotes will perform an implementation defined search then fallback to the (implementation defined) search method used by I think in general this looks something like |
Sorry, something went wrong.
Use the same format for Python header files
https://bugs.python.org/issue43322