[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-11-21 Thread Éric Araujo
Éric Araujo added the comment: Thanks, done as r86662 and [fbcddbb92b14]. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-11-21 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Nov 21, 2010, at 11:02 PM, Éric Araujo wrote: >I noticed in the output of pydoc that get_makefile_filename does not have a >docstring. I added one in my local copy (“Return the path of the Makefile.”) >and also removed “s” in verbs in other docstrings to c

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-11-21 Thread Éric Araujo
Éric Araujo added the comment: I noticed in the output of pydoc that get_makefile_filename does not have a docstring. I added one in my local copy (“Return the path of the Makefile.”) and also removed “s” in verbs in other docstrings to comply with PEP 257. Shall I commit it? -- Ad

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-10-21 Thread Éric Araujo
Éric Araujo added the comment: Committed in distutils2/_backport/sysconfig.py as [4ef3e9e41c10]. I’ll push this week-end. -- components: +Distutils2 status: pending -> closed versions: +3rd party ___ Python tracker

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-20 Thread Éric Araujo
Éric Araujo added the comment: Will backport to distutils2 shortly and close again. -- assignee: barry -> eric.araujo status: closed -> pending ___ Python tracker ___ ___

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-20 Thread Éric Araujo
Éric Araujo added the comment: Sorry for being out of touch. I’m fine with the new feature here and now; we still have the deprecation process if we want to make both get_config_h_filename and get_makefile_filename private later (as implementation details), or we could have them return None

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-20 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: r84925 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-20 Thread Antoine Pitrou
Antoine Pitrou added the comment: > >On the other hand, this begs the question of why you want to access > >the Python makefile at all. Is there any information in there that > >isn't currently exposed? I think it would be nice if people could > >completely forget about the existence of that fil

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-20 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Sep 18, 2010, at 12:23 PM, Antoine Pitrou wrote: >Antoine Pitrou added the comment: > >Barry's request looks reasonable. Any build information will have >platform specificities to it. Thanks. I'll take that as approval to land it. :) >On the other hand,

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-18 Thread Antoine Pitrou
Antoine Pitrou added the comment: Barry's request looks reasonable. Any build information will have platform specificities to it. On the other hand, this begs the question of why you want to access the Python makefile at all. Is there any information in there that isn't currently exposed? I

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-17 Thread Barry A. Warsaw
Changes by Barry A. Warsaw : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Sep 16, 2010, at 08:27 PM, Éric Araujo wrote: >Éric Araujo added the comment: > >> I don't agree that it's a bad thing that sysconfig exposes >> implementation specific information - it seems kind of the point of >> it. > >Well, it exposes configuration in

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Éric Araujo
Éric Araujo added the comment: > I don't agree that it's a bad thing that sysconfig exposes > implementation specific information - it seems kind of the point of it. Well, it exposes configuration information, for example paths (which should exist in all VMs), but things like the existence of

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Barry A. Warsaw
Changes by Barry A. Warsaw : Added file: http://bugs.python.org/file18904/docs.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: Patch attached. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: I don't agree that it's a bad thing that sysconfig exposes implementation specific information - it seems kind of the point of it. "The sysconfig module provides access to Python’s configuration information like the list of installation paths and the configu

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Barry A. Warsaw
Changes by Barry A. Warsaw : -- keywords: +patch Added file: http://bugs.python.org/file18903/9877.diff ___ Python tracker ___ ___ Pyth

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Benjamin Peterson
Benjamin Peterson added the comment: Yes, it's unfortunate that that is exposed. Hopefully, sysconfig will evolve some way to find information independent of implementation. -- ___ Python tracker _

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Sep 16, 2010, at 06:15 PM, Benjamin Peterson wrote: >-1 The Makefile is very implementation specific to CPython. and pyconfig.h isn't? -Barry -- ___ Python tracker _

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Benjamin Peterson
Benjamin Peterson added the comment: -1 The Makefile is very implementation specific to CPython. -- nosy: +benjamin.peterson ___ Python tracker ___ __

[issue9877] Expose sysconfig._get_makefile_filename() in public API

2010-09-16 Thread Barry A. Warsaw
New submission from Barry A. Warsaw : sysconfig.get_config_h_filename() returns the path of pyconfig.h. The Makefile is also used to return values from sysconfig but it's path is hidden in a non-public method, for no good reason that I can think of. Therefore, sysconfig._get_makefile_filenam