Marc-Andre Lemburg added the comment: On 02.12.2014 19:46, Antoine Pitrou wrote: > >> Note that on Linux, 32-bit and 64-bit versions are typically placed >> into different directory trees > > By whom? Our standard installer doesn't (it uses ../lib/python-X.Y for all > builds).
By the system vendors. Packages (with extensions) will automatically pick up their configuration. > Also, one of the problems (and actually the problem which triggered this > tracker entry) is when doing development inside a working copy (either > through "setup.py develop" or "setup.py build_ext --inplace" - both copy C > extensions directly into the source tree). Fair enough; it's a rare use case, but may be worth supporting. My main point was that we shouldn't start adding tags for e.g. PPC, Intel, ARM, etc. since platforms needing to support multiple such architectures will typically support fat builds anyway. How about using these flags: b0 - 16-bit b1 - 32-bit b2 - 64-bit b3 - 128-bit and so on ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22980> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
