[issue34417] imp.find_module reacts badly to iterator

2018-08-21 Thread Phillip M. Feldman
Phillip M. Feldman added the comment: My apologies for the tone of my remark. I am grateful to you and others who donate their time to develop the code. I'm attaching the wrapper code that I created to work around the problem. Phillip def expander(paths='./*'): """ OVERVIEW This

[issue34417] imp.find_module reacts badly to iterator

2018-08-21 Thread Brett Cannon
Brett Cannon added the comment: Saying "the available functionality is massively inefficient" is unnecessarily hostile towards those of us who actually wrote and maintain that code. Without diving into the code, chances are that requirement is there so that the C code can use macros to

[issue34417] imp.find_module reacts badly to iterator

2018-08-20 Thread Phillip M. Feldman
Phillip M. Feldman added the comment: It appears that the `importlib` package has the same issue: One can't provide an iterator for the path. When searching a large folder tree for an item that is likely to be found early in the search process (i.e., at a high level in the folder tree), the

[issue34417] imp.find_module reacts badly to iterator

2018-08-17 Thread Eric Snow
Eric Snow added the comment: There are several issues at hand here, Phillip. I'll enumerate them below. Thanks for taking the time to let us know about this. However, I'm closing this issue since realistically the behavior of imp.find_module() isn't going to change, particularly in Python

[issue34417] imp.find_module reacts badly to iterator

2018-08-16 Thread Phillip M. Feldman
New submission from Phillip M. Feldman : `imp.find_module` goes down in flames if one tries to pass an iterator rather than a list of folders. Firstly, the message that it produces is somewhat misleading: RuntimeError: sys.path must be a list of directory names Secondly, it would be