[issue34211] Cygwin build broken due to use of &PyType_Type in static declaration in _abc module
Erik Bray
report at bugs.python.org
Tue Jul 24 13:00:16 EDT 2018
New submission from Erik Bray <erik.m.bray at gmail.com>:
This is essentially the same as issue21124, but introduced more recently with the addition of the _abc_data_type in the _abc module.
The workaround is simply to use PyVarObject_HEAD_INIT(NULL, 0) instead of PyVarObject_HEAD_INIT(&PyType_Type, 0); PyType_Ready should take care of the rest.
P.S. I'm trying to get going again on the project of adding an AppVeyor build, and eventually a buildbot for Cygwin. My previous attempt was doomed because I wanted to fix all failing tests on Cygwin *first*. This time I am going for a more "instant gratification" approach of just skipping the tests that fail (for now) so that I can at least catch new regressions, and then gradually re-enabled skipped tests as I can find fixes for them.
However, for that to happen we at least need a minimal build to work.
----------
components: Build
keywords: 3.7regression
messages: 322315
nosy: erik.bray
priority: normal
severity: normal
stage: needs patch
status: open
title: Cygwin build broken due to use of &PyType_Type in static declaration in _abc module
type: compile error
versions: Python 3.7, Python 3.8
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34211>
_______________________________________
More information about the Python-bugs-list
mailing list