[Twisted-Python] More trial problems with 8.0.1

Brian Granger ellisonbg.net at gmail.com
Thu Apr 10 17:23:58 EDT 2008

On Thu, Apr 10, 2008 at 2:49 PM, Jean-Paul Calderone <exarkun at divmod.com> wrote:
> On Thu, 10 Apr 2008 14:44:45 -0600, Brian Granger <ellisonbg.net at gmail.com>
> wrote:
> > Hi,
> >
> > Earlier today I posted about a problem with trial.  I reinstalled
> > 8.0.1 and the origianl problem has gone away.  Now I get the following
> > error.  It appears that trial is trying to write something to the
> > plugins directory.  But that doesn't (and shouldn't) have the correct
> > write permissions.  I can run trial with as sudo, but not as a regular
> > user.  Isn't it bad practice to rely on being able to write to
> > site-packages at runtime.  Shouldn't such things do into a .twisted
> > directory or something like that?
> >
>  See the plugin cache section of the plugin howto documentation:
> http://twistedmatrix.com/projects/core/documentation/howto/plugin.html#auto3
>  Specifically, the paragraph about site-wide installations.
>  Jean-Paul

OK, there is documentation, but I still don't think it is a good idea
to rely on write permissions in this way.  Examples:

1) User downloads the Mac OS X installer for twisted from the twisted
web site.  They install it and run trial and get this nasty exception
about write permissions.  This installer installs into the system-wide
sitepackages and user will basically _always_ get this problem.

2)  User installed twisted by doing "sudo easy_install Twisted"  They
too get the exception anytime they run trial.

3) User installs using the tarball and installs using the standard
"sudo python setup.py install."  They get it too, unless they add an
optional argument to have twisted installed in their home directory
some place.

The bottom line is that these installation routes are not exceptional,
they are the most common ones.  This approach almost ensures that
almost all of our users will observe this exception when they run our
(ipython1's) test suite.  The same will be true of any twisted using
project that relies on trial or (likely) the plugin architecture.

This behavior may be documented, but I still think it is a bad idea.

Am I misunderstanding something?



>  _______________________________________________
>  Twisted-Python mailing list
>  Twisted-Python at twistedmatrix.com
>  http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

More information about the Twisted-Python mailing list