Author rdb
Recipients rdb
Date 2018-12-02.15:00:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1543762855.5.0.788709270274.issue35376@psf.upfronthosting.co.za>
In-reply-to
Content
If modulefinder finds a nested module import (eg. 'import a.b.c') while there is a top-level module with the same name (eg. 'c') that failed to import and got added to the badmodules list, it will skip it entirely without even trying to import it.

This has a trivial fix (attached).  The right thing to do is clearly to check it by fqname in the badmodules dict since that's also what it expects in other locations.

I can make a PR as soon as my CLA gets validated, if that is more convenient.  (Which branch should I make the PR against?)
History
Date User Action Args
2018-12-02 15:00:55rdbsetrecipients: + rdb
2018-12-02 15:00:55rdbsetmessageid: <1543762855.5.0.788709270274.issue35376@psf.upfronthosting.co.za>
2018-12-02 15:00:55rdblinkissue35376 messages
2018-12-02 15:00:55rdbcreate