A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2019-February/156346.html below:

[Python-Dev] Is distutils.util.get_platform() the "current" or the "target" platform

[Python-Dev] Is distutils.util.get_platform() the "current" or the "target" platform [Python-Dev] Is distutils.util.get_platform() the "current" or the "target" platformNick Coghlan ncoghlan at gmail.com
Sat Feb 16 11:31:18 EST 2019
On Sat, 16 Feb 2019 at 08:06, Steve Dower <steve.dower at python.org> wrote:
> I'm inclined to say that nobody but us uses this API :) Does that make
> it seem more okay to "clarify" that it's returning target platform?

I've always treated the situation as "Cross-compilation doesn't work,
build on the target platform, using a VM if you have to", and I
suspect a lot of folks have approached the status quo the same way.

So if there are functions you can change to make cross-compilation
actually work without requiring changes to a lot of other projects,
that seems like a good thing to me.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4