I recently cut over to using distutils to distribute open-source software. distutils decided to create an zipimporter egg. (Well, I&#39;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&#39;t really exist. Is there something I did to create this improperly or perhaps this just they things are? <br>
<br>For concreteness, select one of the eggs at <a href="http://code.google.com/p/pytracer">http://code.google.com/p/pytracer</a> and install one of these.<br><br>I did this on GNU/Linux and Python 2.5 and I look at the co_filename of one of the methods:<br>
<br><br>&gt;&gt;&gt; import tracer<br>&gt;&gt;&gt; tracer.__dict__[&#39;size&#39;].func_code.co_filename<br>&#39;build/bdist.linux-i686/egg/tracer.py&#39;<br><br>But there is no file called &quot;build/bdist.linux-686/egg/tracer.py&quot; in the filesystem. Instead there is a member &quot;tracer.py&quot; inside <br>
/usr/lib/python2.5/site-packages/tracer-0.1.0-py2.5.egg&#39;. Is there something I could to do cause this to happen? <br><br>Related is the question is how one can determine the file location of an egg and the member for a given import. It looks to me that there is no standard way defined to do this across loaders that work with some sort of single archive like a single zipped egg.<br>
<br>Is this correct? <br>