PJ Eby <pje <at> telecommunity.com> writes: > not just the one of current interest. Beyond that, keeping the > description in a separate file will keep any loads that do happen fast > (how often is the long description currently needed by anything other > than PyPI?), and entry keeping entry points in separate files should > minimize the number of loads when searching for entry points. (Since > in general the entry points you're looking for are needles in a > haystack, it pays to not have to inspect every stalk of hay, but > instead proceed directly to the bits that are metal. )
Presumably the overhead for entry points is only relevant for scanning installed distributions looking for entry points? In my JSON metadata format, I currently have the entry points data as an "exports" sub-dictionary in the main meta-dictionary, but this is written to a separate file during installation so that only that small part of the metadata needs to be checked when e.g. iterating over entry points in a group. Regards, Vinay Sajip _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
