[issue22148] frozen.c should #include instead of "importlib.h"

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 t

[issue22148] frozen.c should #include instead of "importlib.h"

John Beck added the comment: Hm, that is strange. My reading of the semantics of 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 require

[issue22148] frozen.c should #include instead of "importlib.h"

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 include; use "quotes" instead #include ^ "importlib.h" 1 error generated. m

[issue22148] frozen.c should #include instead of "importlib.h"

Changes by Brett Cannon : -- assignee: -> brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue22148] frozen.c should #include instead of "importlib.h"

Changes by Antoine Pitrou : -- nosy: +brett.cannon, eric.snow, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue22148] frozen.c should #include instead of "importlib.h"

Changes by Shawn : -- nosy: +swalker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/ma

[issue22148] frozen.c should #include instead of "importlib.h"

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", et