<div class="gmail_quote">On Wed, Mar 14, 2012 at 8:21 AM, Paul Moore <span dir="ltr"><<a href="mailto:p.f.moore@gmail.com">p.f.moore@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">One thing I dislike about eggs is that the filename includes a Python<br></div>
version for all eggs, even when the package is pure python. I know<br>
eggs contain .pyc files (which are version specific) but IMO they<br>
shouldn't.</blockquote><div><br></div><div>Your objection would make sense if .egg files were simply a format for transmitting files to be installed someplace -- in which case they could've omitted the .pyc files.</div>
<div><br></div><div>.egg files were originally designed as a plugin distribution format, which means they're supposed to be drop-in usable to an app's plugin directory.</div><div><br></div><div>Which brings up a few questions, actually. Will these .pbd files be drop-in usable in the same way? If not, then they're not really replacing eggs. The same is true if they don't offer plugin discovery metadata like entry points or EggTranslations.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Having a python version in the filename where it's not<br>
necessary increases the maintenance burden on packagers, who have to<br>
generate the extra files, </blockquote><div><br></div><div>This is a bit of a misconception, perhaps originating in the fact that setuptools itself was always distributed as a collection of version-specific eggs. This was done solely to ease the bootstrapping of setuptools itself (to avoid recursively invoking the distutils while trying to build another package), and isn't really necessary for easy_install or other tools. You only need to generate eggs if you are supporting a binary application of some kind.</div>
<div><br></div><div>Again, this raises the question: is .pbd a load-and-go format for distributing and *running* Python code, or is it just a way to bundle compiled extensions along with source code to simplify installation? I worry that some folks in the conversation may be thinking one thing, and some folks the other.</div>
<div><br></div></div>