This is useful information and thanks for suggesting the workaround.<br><br>However this does not address the issue which is not about how I can create an unzipped egg for my use or the use of others. (Or what I did or didn't do to create such an zipped egg).<br>
<br>I am interested in writing tools that work with both zipped an unzipped eggs. To the extent that setuptools/distutils is responsible for setting the co_filename field in the code object what should go inside that field? And how can a programmer reliably and, if possible, uniformly untangle this to get/report a location. <br>
<br><div class="gmail_quote">On Tue, Dec 23, 2008 at 9:14 AM, zooko <span dir="ltr"><<a href="mailto:zooko@zooko.com">zooko@zooko.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Dec 22, 2008, at 20:51 PM, Rocky Bernstein wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I recently cut over to using distutils to distribute open-source software. distutils decided to create an zipimporter egg. (Well, I'm sure it did what it did for good reason, I just am not all that aware of what I did to cause it too choose that.) When I inspect functions in that egg they seem to have a path that doesn't really exist. Is there something I did to create this improperly or perhaps this just they things are?<br>
</blockquote>
<br></div>
This is one of the parts of issue33:<br>
<br>
<a href="http://bugs.python.org/setuptools/issue33" target="_blank">http://bugs.python.org/setuptools/issue33</a><br>
<br>
I just added the following comment to that issue ticket:<br>
<br>
Suggested workaround for people finding this ticket from a search engine query<br>
such as "distutils zip problem":<br>
<br>
1. Put the following in your distutils config file:<br>
<br>
{{{<br>
[easy_install]<br>
zip_ok=False<br>
}}}<br>
<br>
Then all packages that you easy_install will be unzipped.<br>
<br>
2. When creating a package for others, pass {{{zip_ok=False}}} to<br>
{{{setup()}}}. This is a bit nasty, because that flag is really supposed to<br>
indicate whether there is something in the package that can't work from zip, and<br>
if you set that flag then this abrogrates the user's preference when installing<br>
-- there is no way for them to tell easy_install to install the package zippedin spite of the {{{zip_ok=False}}} flag. However, I have seen so many reports<br>
of problems with zip files, and zero reports of problems with unzipped files,<br>
and zero requests for zipped files, so I'm personally comfortable setting<br>
{{{zip_ok=False}}} just to help the user avoid the problems.<br>
</blockquote></div><br>