[issue4359] at runtime, distutils uses buildtime files

Éric Araujo added the comment: ... and #9807 spawned #9878. -- superseder: deriving configuration information for different builds with the same prefix -> Avoid parsing pyconfig.h and Makefile by autogenerating extension module ___ Python tracker

[issue4359] at runtime, distutils uses buildtime files

Changes by Éric Araujo : -- superseder: -> deriving configuration information for different builds with the same prefix ___ Python tracker ___ __

[issue4359] at runtime, distutils uses buildtime files

Éric Araujo added the comment: #9807 has been recently opened. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue4359] at runtime, distutils uses buildtime files

Éric Araujo added the comment: I think the future sysconfig module (http://bitbucket.org/tarek/distutils2/src/tip/docs/design/wiki.rst) addresses part of the issue: It will use a configparser file to store installation directories. There is nothing about other build-time variables, though; th

[issue4359] at runtime, distutils uses buildtime files

Toshio Kuratomi added the comment: Hey tarek, the main thrust of this bug for me was storing the data in an inappropriate format and not having an API to get at it; things that I think the sysconfig branch will address. Does it make sense to have a bug to track that progress? Does it make sens

[issue4359] at runtime, distutils uses buildtime files

Tarek Ziadé added the comment: I am closing this since Fedora has fixed the issue on their side. On a side note: I am working on this new sysconfig module, in a branch called tarek_sysconfig -- status: open -> closed ___ Python tracker

[issue4359] at runtime, distutils uses buildtime files

Tarek Ziadé added the comment: see http://mail.python.org/pipermail/python-dev/2009-November/094232.html (notice that the dependency in install can be removed easily because it just reads variables from sys and does not require to import sysconfig) -- _

[issue4359] at runtime, distutils uses buildtime files

Tarek Ziadé added the comment: This is a problem indeed. One solution would be to generate a module in the stdlib that contains all these info, when configure is called. as a matter of fact, I am currently working in a branch to add a module called "sysconfig" to the stdlib, that contains ins

[issue4359] at runtime, distutils uses buildtime files

Dave Malcolm added the comment: > For Fedora, I've fixed this (I hope) by special-casing those two files: Sorry; for "fixed", read "addressed"; this covers part 1 of the issue, but not part 2. -- ___ Python tracker

[issue4359] at runtime, distutils uses buildtime files

Dave Malcolm added the comment: For Fedora, I've fixed this (I hope) by special-casing those two files: %{_libdir}/python%{pybasever}/config/Makefile /usr/include/python2.6/pyconfig-{32|64}.h making them part of the core python package. See downstream bug here: https://bugzilla.redhat.com/sh

[issue4359] at runtime, distutils uses buildtime files

Andrew McNabb added the comment: I've noticed this, too, and I agree with Toshio's observations. Tarek, do you have any opinions? -- nosy: +amcnabb ___ Python tracker ___ __

[issue4359] at runtime, distutils uses buildtime files

Changes by Tarek Ziadé : -- assignee: -> tarek nosy: +tarek versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 -Python 2.5 ___ Python tracker ___ _

[issue4359] at runtime, distutils uses buildtime files

New submission from Toshio Kuratomi <[EMAIL PROTECTED]>: When using some distutils functions, distutils attempts to use buildtime files like Makefile and pyconfig*.h as data sources. For instance, this snippet:: from distutils.command.install import install from distutils.core import Distri