[tahoe-lafs-trac-stream] [tahoe-lafs] #1405: python setup.py --help-commands raises exception
tahoe-lafs
trac at tahoe-lafs.org
Mon May 16 13:21:18 PDT 2011
#1405: python setup.py --help-commands raises exception
--------------------------+------------------------------------------------
Reporter: zooko | Owner: davidsarah
Type: defect | Status: new
Priority: minor | Milestone: undecided
Component: | Version: 1.8.2
packaging | Keywords: packaging setuptools docs reviewed
Resolution: |
Launchpad Bug: |
--------------------------+------------------------------------------------
Comment (by davidsarah):
Replying to [comment:2 zooko]:
> Does anyone know why the "upload_docs" command is broken? I don't know
where it is even defined or how it got into my (Ubuntu Natty) system. It
isn't defined in the tahoe-lafs codebase or the zetuptoolz codebase.
That's the trouble with loading extensions from random code on the
sys.path. (I'm not even going to look at how setuptools decides what to
load; it would probably upset me.)
> We should presumably report a bug to its author...
It appears to be part of setuptools. I can't find any documentation for it
in setuptools, but the documentation for the corresponding command in
Distutils2 is
[http://packages.python.org/Distutils2/distutils/newcommands.html#upload-
docs-upload-package-documentation-to-pypi here]. So the author is probably
either PJE or Tarek.
> Otherwise, the attachment:tolerate-exceptions-in-help-
commands.darcs.patch seems pretty good. Should we catch more specifically
{{{ImportError}}} instead of all exceptions for now?
I don't know that loading a broken command would necessarily throw
{{{ImportError}}}. The wider catch seems fine to me for {{{--help-
commands}}}; note that actually trying to use the command would throw the
original exception.
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1405#comment:3>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list