[issue23287] ctypes.util.find_library needlessly call crle on Solaris

Martin Panter added the comment: Do you have an opinion of the proposal Shawn? Judging by John’s “[the constant] is what the system provides, though users may customize as needed”, it sounds like the patch is more than a bug fix. Will it also mean find_library() will no longer search

[issue23287] ctypes.util.find_library needlessly call crle on Solaris

Shawn added the comment: Could we get someone to evaluate this please? -- nosy: +swalker ___ Python tracker ___

[issue23287] ctypes.util.find_library needlessly call crle on Solaris

John Beck added the comment: First, there are two related but somewhat separate issues here. Regarding the patches attached to http://bugs.python.org/issue20664 they seem fine. In theory, they should not be needed, as though it is true that dump(1) moved from /usr/ccs/bin to /usr/bin in

[issue23287] ctypes.util.find_library needlessly call crle on Solaris

Jeff Quast added the comment: John, What do you think of the patches attached to http://bugs.python.org/issue20664 ? crle is not needed at all because the default library path is a constant on Solaris I don't believe this to be true, source? crle is absolutely needed to add additional

[issue23287] ctypes.util.find_library needlessly call crle on Solaris

Jeff Quast added the comment: I looked over the focus on default path, thank you for clarifying! Sadly, I can't help you move either of these patches forward, best wishes! -- ___ Python tracker rep...@bugs.python.org

[issue23287] ctypes.util.find_library needlessly call crle on Solaris

New submission from John Beck: On Solaris, in Lib/ctypes/util.py, we have code that looks for /usr/bin/crle and calls it to parse its output to try to determine the Default Library Path. This code broke recently (Solaris 12 build 65), as it expects to find a line starting with Default