[vistrails-dev] [GIT] VisTrails: <bugfix>Fixed issue with forced versions on modules</bugfix>

git-noreply at vistrails.org git-noreply at vistrails.org
Thu Jan 12 20:07:20 EST 2012


The project "VisTrails":

The branch, master has been updated
       via  4ae602caa09e9bb77fb4be8875945659c8096a5e (commit)
      from  5bcaa7e75c6de7904548e5734751e735833cd1a8 (commit)


- Log -----------------------------------------------------------------
commit 4ae602caa09e9bb77fb4be8875945659c8096a5e
Author: David Koop <dakoop at cs.utah.edu>
Date:   Thu Jan 12 18:02:34 2012 -0700

<bugfix>Fixed issue with forced versions on modules</bugfix>

In 2.0, modules from workflows that do not have package version information (workflows produced in earlier versions of VisTrails) must now have version information and are upgraded to do so.  There was an issue with the check for version information (checking == '' and not == None) which is now fixed.

core/vistrail/pipeline.py:
- Pipeline.ensure_modules_are_on_registry: check if evaluating
module.version as a boolean is False rather than if
module.version == '', this captures None and ''

-----------------------------------------------------------------------

Summary of changes:
 vistrails/core/vistrail/pipeline.py |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

-- 
VisTrails


More information about the vistrails-dev mailing list