On Wed, Feb 25, 2004 at 08:39:22PM -0700, Eric Mangold wrote:My idea for allowing greater flexibility is to bundle the actual zshcompletion functionality as part of the Twisted distribution and give zsha "stub" that will use the completion functions that are bundled with Twisted.Would it not make more sense to get your extensions bundled with Twisted and then installed in the site-functions directory? This is what the FreeBSD portupgrade commands do and it works great!
I've considered this, however I don't believe it is ideal for this specific situation. There are a couple different scenarios where using the completion info installed by Twisted's installion routine would be undesireable.
First, there's no guarantee that the user even has Twisted /installed/. It is very common for the users and developers of Twisted to be working directly out of a CVS checkout. They will do this by adding the directory containing the CVS checkout to their PYTHONPATH env var.
Secondly, the user may have a release version of Twisted installed yet be using another version somewhere else. Such as CVS or having simply extracted a newer Twisted release tarball in their home dir and set PYTHONPATH accordingly.
So asking python is the only sure way to provide info that is accurate for what the user is presently doing.
-Eric