➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Phillip.M.Feldman@gmail.com
Recipients Phillip.M.Feldman@gmail.com, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-03-13.16:40:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAB2ViTbT7_pTwtj7u_ccH9o2mCojcU8M+=nmdttjvzH8fVfO3A@mail.gmail.com>
In-reply-to <1552405335.67.0.560488913178.issue36266@roundup.psfhosted.org>
Content 
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@bugs.python.org> wrote:

>
> Steve Dower <steve.dower@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@bugs.python.org>
> <https://bugs.python.org/issue36266>
> _______________________________________
>
History
Date User Action Args
2019-03-13 16:40:10Phillip.M.Feldman@gmail.comsetrecipients: + Phillip.M.Feldman@gmail.com, paul.moore, tim.golden, zach.ware, steve.dower
2019-03-13 16:40:10Phillip.M.Feldman@gmail.comlinkissue36266 messages
2019-03-13 16:40:10Phillip.M.Feldman@gmail.comcreate