[wingide-users] Dealing with eggs
walkerh at picoscript.com
Thu Aug 24 09:20:50 MDT 2006
If having the uncompressed egg turns out to be problematic, I believe there
is another less pleasant option.
Isn't it possible to create .pi files that serve to document the interfaces
for Wing? I remember that Wing comes with several .pi files that document
the non-Python parts of the standard library. This is how auto completion
works for dict and list.
Of course creating (and maintaining) such files is so tedious, that just
adding an extracted egg to your sys.path is usually the better option. IMHO,
you would only do this if either (1) trickery inside the .py files confused
Wing or (2) adding the .py files to your path somehow caused problems.
From: wingide-users-bounces at wingware.com
[mailto:wingide-users-bounces at wingware.com] On Behalf Of Wingware Support
Sent: Thursday, August 24, 2006 9:40 AM
To: Matt Feifarek
Cc: wingide-users at wingware.com
Subject: Re: [wingide-users] Dealing with eggs
On Wed, 23 Aug 2006, Matt Feifarek wrote:
> On 8/23/06, Wingware Support <support at wingware.com> wrote:
> > We hope to add egg and zip support as soon as possible as this seems
> > to be more and more common (but of course it's lower priority than
> > things for which there is no work-around).
> So, is the recommended work-around to just extract the egg into
> someplace on sys.path?
For the moment, yes.
More information about the wingide-users