[issue8406] Make some setup.py paths exclude-able

Matthias Bussonnier added the comment: > [2 nice response] Thanks for the nice responses, we all know it can be hard to find the right balance between making a concise comment, and being delicate enough. Thanks all for your hard work on CPython, and looking forward to have time to contribut

[issue8406] Make some setup.py paths exclude-able

Ronald Oussoren added the comment: I'm sorry if my comment was too harsh, it wasn't intended as such. I was surprised at seeing a number of e-mails about issues that were closed because they were out of date. I don't agree with closing old issues when there is actionable content in them becau

[issue8406] Make some setup.py paths exclude-able

R. David Murray added the comment: No, no trouble. We appreciate Carol's efforts! As you say, any changes can be reversed; we prefer that people exercise triage privileges and make mistakes than that they feel too cautious to do anything. If our tone came across as confrontational that was

[issue8406] Make some setup.py paths exclude-able

Matthias Bussonnier added the comment: > We regularly close issues that are 1+ year old on Jupyter/IPython or rescope > the issue to be actionable for contribution. Sorry if me doing that on IPython/Jupyter recently have put you (willingc) in a bad position in here, sincere apologies, you are

[issue8406] Make some setup.py paths exclude-able

Carol Willing added the comment: Fair enough. Ronald and David, I respect your suggestions and thoughts, and I will not triage or close old issues. FWIW, I was trying to be helpful. We regularly close issues that are 1+ year old on Jupyter/IPython or rescope the issue to be actionable for con

[issue8406] Make some setup.py paths exclude-able

R. David Murray added the comment: Heh, that should have been "only close an old issue that hasn't been otherwise resolved if...". -- ___ Python tracker ___ _

[issue8406] Make some setup.py paths exclude-able

R. David Murray added the comment: Right. Only close an issue if there is an existing open issue that addresses the topic better. Age alone is never a criteria for closing issues. Since Ronald agrees the other issue is enough we'll leave this closed, but it wouldn't be crazy to reopen it eit

[issue8406] Make some setup.py paths exclude-able

Ronald Oussoren added the comment: Did you create that new issue? If not this feature request will likely be forgotten. Hmmm... Issue7713 appears to be good enough for remembering that there is a problem with the way setup.py looks for libraries. --

[issue8406] Make some setup.py paths exclude-able

Carol Willing added the comment: Ronald, while I may have closed this issue prematurely in other folks' view, I did not do so without thought or reflecting if the issue was relevant. My recommendation to close the issue was based on several factors: - the desire to assist triaging issues that

[issue8406] Make some setup.py paths exclude-able

Ronald Oussoren added the comment: I don't understand why this issue was closed. Apparently it was closed because it is an old issue without checking if the issue is still relevant??? To be honest the way setup.py looks for libraries could use some attention, the current methods is a bit too m

[issue8406] Make some setup.py paths exclude-able

R. David Murray added the comment: We don't close issues just because they are languishing. We'd need to know that the issue has been superseded or is otherwise no longer an issue. It sounds like this one falls into that category, since another issue is noted as a possible superseder, but I

[issue8406] Make some setup.py paths exclude-able

Changes by Carol Willing : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8406] Make some setup.py paths exclude-able

Carol Willing added the comment: This issue is languishing. Recommend closing the issue. -- nosy: +willingc ___ Python tracker ___ ___

[issue8406] Make some setup.py paths exclude-able

Changes by Éric Araujo : -- nosy: +eric.araujo versions: +Python 3.2 -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8406] Make some setup.py paths exclude-able

Changes by Skip Montanaro : -- nosy: -skip.montanaro ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue8406] Make some setup.py paths exclude-able

Ned Deily added the comment: Sorry, Ronald, of course that's what you were suggesting with the proposed configure --with options. +1 on that. I'd just want to ensure that any solution addresses any needs in Issue7713, too. Something like that should. There are probably other open issues i

[issue8406] Make some setup.py paths exclude-able

Ned Deily added the comment: Skip, I saw David's chroot remark but I'm having a hard time envisioning how one could use that as a practical matter to build an OS X framework without some *serious* changes to the current configure(s), Makefile(s), and installer script. -- ___

[issue8406] Make some setup.py paths exclude-able

Ned Deily added the comment: Ronald, as far as I can see, the patch as it stands only addresses dbm so more work is needed to address all the other cases, the ones that actually matter. Issue7713 describes a more serious, general problem because a number of other builders / distributers have

[issue8406] Make some setup.py paths exclude-able

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue8406] Make some setup.py paths exclude-able

Skip Montanaro added the comment: Ronald> To be honest I'd must rather remove /opt/local and /sw entirely Ronald> from setup.py and add new configure flags to specify the Ronald> location of a number of libraries (e.g. 'configure Ronald> --with-sleepycat-db=/opt/local'). Explicit co

[issue8406] Make some setup.py paths exclude-able

Ronald Oussoren added the comment: Ned: the patch does have a (positive) effect when building the OSX installer: the build-installer script creates private builds of a number of libraries, but setup.py can detect other libraries (such as libintl) as well and we don't guard against that at the

[issue8406] Make some setup.py paths exclude-able

Ned Deily added the comment: Without testing it, I'd guess the patch wouldn't hurt but it also wouldn't affect the OS X installer build as the installer script builds a local copy of Sleepycat db4 (since none is included in OS X) and supplies it as an additional local library/include file whi

[issue8406] Make some setup.py paths exclude-able

Skip Montanaro added the comment: The patches referenced in issue7713 just unconditionally delete certain directories from the search path(s). This patch (now attached) allows the user to control that. I presume, for instance, if the MacPorts folks don't want /usr/X11/... in search paths that

[issue8406] Make some setup.py paths exclude-able

Skip Montanaro added the comment: Let's try this again. -- keywords: +patch Added file: http://bugs.python.org/file16930/setup.diff ___ Python tracker ___ ___

[issue8406] Make some setup.py paths exclude-able

Ned Deily added the comment: I think this is essentially a duplicate of Issue7713. (Also there doesn't seem to be an "attached".) -- nosy: +ned.deily ___ Python tracker ___ _

[issue8406] Make some setup.py paths exclude-able

New submission from Skip Montanaro : The topic of the vileness of Fink or MacPorts came up in python-dev when discussing building a Mac installer. I remembered that a couple /sw and /opt/local directories are searched unconditionally, making it a bit more challenging for someone to create a fram