<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>Thanks, I think I'm getting it.</div><div id="AppleMailSignature"><br></div><blockquote type="cite"><div><div dir="ltr">About the toml file... the *-info metadata is a compiled artifact, according to all the existing Python packages. Most sdists even have a *.egg-info directory.</div></div></blockquote><div><br></div><div>If it's a compiled artifact, then shouldn't it NOT be in a source dist?</div><br><blockquote type="cite"><div><div dir="ltr"> It is inconvenient if you want to know the true dependencies without running setup.py. </div></div></blockquote><div><br></div><div>Isn't that what the toml file is for? </div><br><blockquote type="cite"><div><div dir="ltr">I think we are stuck with it, and it's not all bad - if there is some useful metadata that doesn't affect the dependency resolver, and it is "too static" or too cumbersome to write out by hand, there's a place to do that.</div></div></blockquote><div><br></div><div>I'm trying to imagine what that info would be, but I suppose there could be meta data about a package that is generated at build time -- maybe info about how it was built, for instance. </div><div><br></div><div>Hmm -- maybe you could put info in there about non-Python shared libs it's linked to, for instance.</div><div><br></div><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Eggs are the only way to add a zipped distribution to PYTHONPATH and have setuptools find the metadata</div></blockquote></div></div></blockquote><div><br></div><div>Can pip find it in a zipped package? Remember, I don't care to support setuptools only features anyway :-)</div><br><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">. Eggs are used by buildout, especially in the unzipped into a directory form</div></blockquote></div></div></blockquote><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">And they could still be used for their originally designed use as a plugin format.</div></blockquote></div></div></blockquote><div><br></div><div>If pkg_resources gets spun off, would it support that?</div><div><br></div><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div> *.egg-info or EGG-INFO is the predecessor of the *.dist-info format designed in PEP-376. <span style="line-height:1.5">You get *.egg-info whenever you install something with setuptools without going through bdist_wheel.</span></div></div></blockquote></div></div></blockquote><div><br></div><div>So setuptools_lite would write a dist_info.</div><div><br></div><div>I take it pip looks for both?</div><div><br></div><div><br></div></div></body></html>