setup.py uses "/sw" by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyOpenSSL |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
"/sw" means fink. setup.py has a hardcoded
if sys.platform == 'darwin':
IncludeDirs = ['/sw/include']
This is very wrong, but presumably usually has no effect. However, I happen to have an old copy of fink stored in /sw on my system. It isn't in any of my paths, and normally when I build projects they use interfaces such as environment variables, commmand-line options or distutils config files so I can control which paths they will search for include dirs, so I haven't noticed this /sw sitting around for a few years. Just now I figured out why pyOpenSSL builds strangely on this machine sometimes -- it looks in /sw even though my distutils config file doesn't say to.
An appropriate fix is probably just to remove that stanza and see if any buildbots change behavior or if any users complain.
Related branches
Changed in pyopenssl: | |
milestone: | none → 0.10 |
Changed in pyopenssl: | |
status: | Fix Committed → Fix Released |
Sorry if this was cryptic.
* "This is very wrong" because using fink is likely to cause problems such as building an unloadable extension module, and fink is widely hated (not by me), and it should not be the default behavior.
* It "usually has no effect" because fink is usually not installed.
* "If any users complain" then we should tell them if they want builds of Python packages to use fink include dirs and lib dirs then they should edit their user or system distutils config file and specify the include_dirs and library_dirs options in the [build_ext] section.