[tahoe-lafs-trac-stream] [tahoe-lafs] #1388: nicer reporting of unparseable version numbers in deps
tahoe-lafs
trac at tahoe-lafs.org
Thu Mar 31 22:50:49 PDT 2011
#1388: nicer reporting of unparseable version numbers in deps
-----------------------------------------------------------+----------------
Reporter: zooko | Owner: nobody
Type: defect | Status: new
Priority: minor | Milestone: undecided
Component: unknown | Version: 1.8.2
Keywords: error usability packaging setuptools foolscap | Launchpad Bug:
-----------------------------------------------------------+----------------
As described in #1387, if one of the dependencies has a version number
that is not considered "Rational" by {{{verlib}}}, Tahoe-LAFS emits
{{{
File "/Users/zooko/playground/tahoe-
lafs/pristine/src/allmydata/__init__.py", line 375, in <module>
check_all_requirements()
File "/Users/zooko/playground/tahoe-
lafs/pristine/src/allmydata/__init__.py", line 373, in
check_all_requirements
raise PackagingError(get_error_string(errors, debug=True))
allmydata.PackagingError:
TypeError: expected string or buffer
}}}
followed by a potentially large and messy-looking dump of the
{{{PYTHONPATH}}}.
It would be better if the error message said that the problem was that a
version number couldn't be parsed, as well as specifying what the version
number was that couldn't be parsed and where it came from.
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1388>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list