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 jeffr@livedata.com
Recipients jeffr@livedata.com, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-08-19.12:43:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566218629.27.0.381481574182.issue37886@roundup.psfhosted.org>
In-reply-to
Content
Python 3.8.0b3 has the fixed https://docs.python.org/3/c-api/tuple.html#c.PyStructSequence_NewType, but one of the documented features of PyStructSequence is the special https://docs.python.org/3/c-api/tuple.html#c.PyStructSequence_UnnamedField which is meant to be used for unnamed (and presumably also "hidden") fields.

However, this variable is not "exported" (via __declspec(dllexport) or the relevant Python C macro) and so my C extension cannot "import" it and use it.

My guess is that this passed testing because the only tests using it are internal modules linked into python38.dll, which are happy with the `extern` in the header:

Include\structseq.h:extern char* PyStructSequence_UnnamedField;
History
Date User Action Args
2019-08-19 12:43:49jeffr@livedata.comsetrecipients: + jeffr@livedata.com, paul.moore, tim.golden, zach.ware, steve.dower
2019-08-19 12:43:49jeffr@livedata.comsetmessageid: <1566218629.27.0.381481574182.issue37886@roundup.psfhosted.org>
2019-08-19 12:43:49jeffr@livedata.comlinkissue37886 messages
2019-08-19 12:43:48jeffr@livedata.comcreate