|
From: | Hartmut Goebel |
Subject: | Re: [PATCH] doc: Add guide how to specify dependencies for Python packages |
Date: | Fri, 7 Oct 2016 09:44:29 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
Hi Ludo,
thanks for the review and for proof-reading :-) I'll send an updated patch in a few days, waiting for some more feedback on this: Am 06.10.2016 um 23:02 schrieb Ludovic Courtès:
My aim was to provide concrete instructions for those wanting to package Python packages. But I will think about how to add some pointer to cross-compilation. From a Python programmers perspective, "cross-compilation" is a non-issue in most cases. Most Python packages are pure Python, will be compiled into byte-code and thus they are platform independent. (Much like .jar files) This is why most python packages are marked as "noarch" in other Linux distributions. As a Python programmer I think in terms of build-time, maybe test-time and run-time. This only exception for this are Python packages containing C-code (called "extension modules"). But I have to admit that I have no clue about cross-compiler these. (I do no even find good introductions on this in the web.) The official Python packaging guide [1] does not really talk about cross-compilation. Only about "Cross-compiling on Windows". [1] https://docs.python.org/3/distutils/builtdist.html -- Regards Hartmut Goebel | Hartmut Goebel | address@hidden | | www.crazy-compilers.com | compilers which you thought are impossible | |
[Prev in Thread] | Current Thread | [Next in Thread] |