Brett Cannon added the comment:
The key point here is that importlib.h isn't installed with the other header
files; it's purely for compilation since it doesn't expose any API. I'm not
sure how you tweaked your build environment to break that assumption, but since
importlib.h is not expected
John Beck added the comment:
Hm, that is strange. My reading of the semantics of foo.h vs
foo.h was that they are almost the same, except that foo.h has
the additional semantic of searching the local directory (wherever
the .c file is that is #include'ing it) first. So if other platforms
Brett Cannon added the comment:
Unfortunately switching to angle brackets breaks on other platforms, e.g. OS X
using Clang:
Python/frozen.c:5:10: error: 'importlib.h' file not found with angled
include; use quotes instead
#include importlib.h
^
importlib.h
1
Changes by Brett Cannon br...@python.org:
--
assignee: - brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22148
___
___
New submission from John Beck:
Background: on Solaris, we build Python and various modules 64-bit. To
make this work with our general 64-bit changes, we use foo/64 as the path
for our shared objects (.so files) rather than foo, for various values
of foo (e.g., /usr/lib, /usr/lib/python3.4,
Changes by Shawn binarycrusa...@gmail.com:
--
nosy: +swalker
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22148
___
___
Python-bugs-list mailing
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +brett.cannon, eric.snow, ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22148
___
___
