[issue36266] Which module could not be found?

Phillip M. Feldman report at bugs.python.org
Wed Mar 13 12:40:10 EDT 2019


Phillip M. Feldman <Phillip.M.Feldman at gmail.com> added the comment:

Hello Steve,

I'm buying only 50 percent of this.  The Python interpreter must know what
module it was trying to import, and can at least be able to report that.

Phillip

On Tue, Mar 12, 2019 at 8:42 AM Steve Dower <report at bugs.python.org> wrote:

>
> Steve Dower <steve.dower at python.org> added the comment:
>
> I agree. Unfortunately, the operating system does not provide this
> information.
>
> The best I can offer is to run Process Monitor [1] and watch its logs. It
> should show the paths it attempts to access.
>
> [1]: http://technet.microsoft.com/en-us/sysinternals/bb896645
>
> ----------
> resolution:  -> third party
> stage:  -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue36266>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36266>
_______________________________________


More information about the Python-bugs-list mailing list