id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
1388	nicer reporting of unparseable version numbers in deps	zooko	somebody	"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."	defect	closed	minor	1.9.0	code	1.8.2	fixed	error usability packaging setuptools foolscap verlib reviewed