[tahoe-lafs-trac-stream] [tahoe-lafs] #1388: nicer reporting of unparseable version numbers in deps

[tahoe-lafs]

#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                                        
   Resolution:           |    Keywords:  error usability packaging setuptools foolscap
Launchpad Bug:           |  
-------------------------+--------------------------------------------------

Comment (by davidsarah):

 It's a bug in {{{verlib}}} that it raises {{{TypeError}}} rather than
 {{{IrrationalVersionError}}}.

 I also agree that it is a bug in {{{check_all_requirements}}} (or
 {{{check_requirement}}}) that the error doesn't say that a version number
 couldn't be parsed, what the number was, or where it came from.

 However, it's not clear to me that it's wrong to print the large and
 messy-looking {{{PYTHONPATH}}} dump. The purpose of that dump is to be
 able to debug path problems on users' machines that might otherwise be
 difficult to reproduce.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1388#comment:1>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage