VisTrails Home

Improve error handling/reporting

From VisTrailsWiki

Revision as of 04:29, 12 November 2010 by Tommy (Talk | contribs)
Jump to: navigation, search
  • Splash screen now shows package initialization
  • Classifying log levels
    • debug 10 (cannot be accessed by setting loglevel)
    • log(info) 20
    • warning 30
    • critical 50
  • ~800 print statements in VisTrails + 200 commented ones


Conversion issues


  • print "module %s already handled. skipping" % module_id - log or warning?
  • debug.critical('Package cannot handle upgrade request. VisTrails will attempt automatic upgrade.') - Should it be critical?


  • if _debug: print 'version_a:', version_a (and a lot of similar) - Is it currently being debugged? remove?


  • print m_i: remove?


  • A lot of print statements are used for installing deb/rpm packages. I am not sure if I can remove any.


  • Print statements are used for installing deb packages. I am not sure if I can remove any.


  • Contains print statements but should this low-level library have a dependency on core/debug?
Personal tools