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 ronaldoussoren
Recipients alexchandel, rhettinger, ronaldoussoren, steven.daprano
Date 2020-07-18.07:27:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1595057274.34.0.123281311611.issue41297@roundup.psfhosted.org>
In-reply-to
Content
modulegraph already knows where the import is done, and users of the library can use that information to make decisions. 

There's no need to make changes to either heapq.py or modulegraph.

For py2app I've made the choice to no be smart about inclusions and just try to include everything that may be imported because disk space is cheap these days.  I just exclude optional dependencies (in py2app, not modulegraph) when I've manually checked that it is safe to do so and the dependency is large.
History
Date User Action Args
2020-07-18 07:27:54ronaldoussorensetrecipients: + ronaldoussoren, rhettinger, steven.daprano, alexchandel
2020-07-18 07:27:54ronaldoussorensetmessageid: <1595057274.34.0.123281311611.issue41297@roundup.psfhosted.org>
2020-07-18 07:27:54ronaldoussorenlinkissue41297 messages
2020-07-18 07:27:54ronaldoussorencreate