[Distutils] Environment marker expression types

[Nick Coghlan]

On Sat, Apr 27, 2013 at 6:43 AM, PJ Eby <pje at telecommunity.com> wrote:
> Actually, while I'm on that subject, I wonder what the parsing
> overhead is going to be for the JSON metadata?  I guess as long as
> it's done in C, it'll probably be ok.  I expect the main runtime
> performance issue for metadata will just be avoiding reading the
> metadata in the first place, by using filename-embedded info so a
> directory read can load the critical info for all available packages,
> 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?)

The current draft still has the long description in the main metadata
file, but you're right, replacing that with a filename relative to the
metadata file may be a better idea. I'll mark it as an open question.

> 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.  ;-) )

Keeping extensions (which will include entry points) in a separate
file is another potentially useful idea.

Cheers,
Nick.

--
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia