Author doko
Recipients Arfrever, barry, brett.cannon, doko, eric.snow, lemburg, ncoghlan, ned.deily, pitrou, python-dev, steve.dower, tim.golden, vstinner, zach.ware
Date 2015-04-13.21:29:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <552C3518.8060803@debian.org>
In-reply-to <1428958897.43.0.431478716646.issue22980@psf.upfronthosting.co.za>
Content
On 04/13/2015 11:01 PM, Antoine Pitrou wrote:
> 
> Antoine Pitrou added the comment:
> 
>> here is the more general approach encoding the triplet into the extension name.
> 
> Thanks. Two comments:
> - is it possible to avoid the hardcoded list? Maintaining this will be a burden

Well, there are two approaches, the one I didn't choose is to derive the triplet
from the $host macro, because people like to build with abi flags as build
parameters, so I choose to entirely base these checks on compiler information.
Currently if you have a new linux architecture you fall back to the same SOABI
as before, which sounds like an acceptable solution.  Or you could fallback to
the $host macro, removing the vendor information.  But then you have two
different methods ...  or we could emit a hard error for unknown linux and
kfreebsd (Debian only) targets, and then extend the check for new architectures.

> - it would be nice to have a test

thought about it, but we only change the SOABI name, and all tests should behave
as before. And because we try to load extensions without the SOABI name, there
is safe fallback.
History
Date User Action Args
2015-04-13 21:29:02dokosetrecipients: + doko, lemburg, barry, brett.cannon, ncoghlan, pitrou, vstinner, tim.golden, ned.deily, Arfrever, python-dev, eric.snow, zach.ware, steve.dower
2015-04-13 21:29:02dokolinkissue22980 messages
2015-04-13 21:29:02dokocreate