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 doko
Recipients Alex.Willmer, doko, vstinner, xdegaye, yan12125, zach.ware
Date 2016-09-13.20:55:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <ae539d32-bd0d-20a2-3639-e2e200f63754@debian.org>
In-reply-to <1473777612.41.0.00487108276248.issue28125@psf.upfronthosting.co.za>
Content
On 13.09.2016 16:40, Xavier de Gaye wrote:
> 
> Xavier de Gaye added the comment:
> 
>> Plus the abi flags should not be set by hand, you'll get in trouble at least for naming extensions, or building extensions for the wrong abi flags. This was an explicit decision when I first started adding the cross-build changes.
> 
> What do you mean ? The abi flags are set by configure and not by hand.
> In which issue is this explicit decision taken, and where is it motivated ?

please try to build extension modules with mismatching abi flags (pydebug is the
relevant one). Post your results for both mismatch cases.

>> So proposing instead to base a cross build on a _PYTHON_MULTIARCH environment variable and deriving the sysconfigdata name on that.
> 
> The _PYTHON_SYSCONFIGDATA_NAME environment variable as the merit to document its purpose with its name. The CPython cross-compilation system is difficult enough to understand that this is a significant advantage.  What are the advantages of introducing this new _PYTHON_MULTIARCH environment variable instead, where else would it be used ?

No, at least it was not difficult when it was created. How did you make it more
difficult?

If we can derive the name, we should do it, not having more special environment
variables when we find the need for it.
History
Date User Action Args
2016-09-13 20:55:59dokosetrecipients: + doko, vstinner, xdegaye, zach.ware, Alex.Willmer, yan12125
2016-09-13 20:55:59dokolinkissue28125 messages
2016-09-13 20:55:59dokocreate