[issue33902] entry_points/console_scripts is too slow

George King added the comment: OK, thanks. I agree that this is best pursued with the developers of the relevant modules. I appreciate your quick and detailed responses! -- ___ Python tracker

[issue33902] entry_points/console_scripts is too slow

Barry A. Warsaw added the comment: "It's complicated" :) But technically speaking they are all separate projects, so while there is synergy, CPython itself *imports* some of those to provide various tasks, but it doesn't lead their development. You'll find a lot of the same players in all

[issue33902] entry_points/console_scripts is too slow

George King added the comment: Thanks Barry. My question then is, what relationship does cpython have with pip, setuptools, distutils and pkg_resources? Since pip comes bundled with Python now it seems a little bit closer than "3rd party". Thanks! --

[issue33902] entry_points/console_scripts is too slow

Barry A. Warsaw added the comment: This really isn't enough information to know exactly what's going on in your case, but there are things that are known to be slow for CLI startups. Probably the biggest contributor is pkg_resources. Of course, that's a third party library that's popular

[issue33902] entry_points/console_scripts is too slow

Change by Eric N. Vander Weele : -- nosy: +ericvw ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33902] entry_points/console_scripts is too slow

New submission from George King : On my newish macOS laptop using Python 3.6 or 3.7, a no-op script takes 3 times as long to invoke using the entry_points machinery as it does to invoke directly. Here are some exemplary times (best times after several tries). $ time python3.6 entrypoint.py