Repository navigation
sysconfig and distutils.sysconfig differ in subtle ways #54050
Description
| BPO | 9841 |
|---|---|
| Nosy | @warsaw, @tarekziade, @merwok |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = 'https://github.com/tarekziade'
closed_at = <Date 2010-09-30.00:40:24.883>
created_at = <Date 2010-09-12.23:26:26.884>
labels = ['library']
title = 'sysconfig and distutils.sysconfig differ in subtle ways'
updated_at = <Date 2010-10-01.23:33:50.900>
user = 'https://github.com/merwok'bugs.python.org fields:
activity = <Date 2010-10-01.23:33:50.900>
actor = 'eric.araujo'
assignee = 'tarek'
closed = True
closed_date = <Date 2010-09-30.00:40:24.883>
closer = 'eric.araujo'
components = ['Distutils', 'Library (Lib)']
creation = <Date 2010-09-12.23:26:26.884>
creator = 'eric.araujo'
dependencies = []
files = []
hgrepos = []
issue_num = 9841
keywords = []
message_count = 5.0
messages = ['116251', '116318', '117681', '117850', '117851']
nosy_count = 3.0
nosy_names = ['barry', 'tarek', 'eric.araujo']
pr_nums = []
priority = 'normal'
resolution = 'wont fix'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue9841'
versions = ['Python 2.7', 'Python 3.2']
Activity
merwok commentedon Sep 12, 2010
With the recent distutils revert, code that was removed from distutils.sysconfig is now back. This causes an unfortunate code duplication that raises maintenance cost (see msg116087 for an example).
Even if distutils is feature-frozen, I think that it should be changed to use the sysconfig module again. Think about it that way: The new feature is sysconfig itself, this does not break the distutils freeze since compatibility would be retained.
tarekziade commentedon Sep 13, 2010
That's what I wanted to do first but it turned out to be a bad idea.
This duplication is unfortunate but the freeze is also to prevent third party code that patches distutils to break.
For instance, there's a lot of code out there that just patches distutils.sysconfig paths... So changing it would break them.
merwok commentedon Sep 30, 2010
I understand. This means that sysconfig fixes will have to be ported to distutils.sysconfig and d2/sysconfig.
tarekziade commentedon Oct 1, 2010
Not in distutils2 because we want to get rid of it, thats the whole point.
distutils2 will use the sysconfig module I've extracted from distutils.
merwok commentedon Oct 1, 2010
By “d2/sysconfig” I meant d2._backport.sysconfig.