Search results
Jump to navigation
Jump to search
- >>> import vcs >>> import cdms22 KB (229 words) - 15:32, 8 July 2008
- import core.modules import core.modules.module_registry5 KB (724 words) - 16:45, 31 January 2007
- <nowiki>from core.modules.vistrails_module import Module from widgets import MyConfigurationWidget13 KB (1,542 words) - 18:44, 7 October 2013
- The server doesn't start because of an import problem. This can be fixed by replacing vistrails/gui/application_server.py in the import section (around line 27), add7 KB (1,036 words) - 17:20, 6 August 2014
- ...umes a vistrail exists which may introduce issues. We have the ability to import workflows from xml so we should be able to create a vistrail from the group ...in the registry list (although they must be in the registry); a user must import them into his own "My Subworkflows" in order to use them in his own work.7 KB (1,110 words) - 18:11, 11 September 2013
- from core.modules.vistrails_module import Module, newModule, \ import core.packagemanager18 KB (2,337 words) - 17:55, 28 April 2014
- ...ges the way the path must be set up, and the syntax that has to be used to import VisTrails packages; safeties are in place to enable old packages that were5 KB (671 words) - 21:09, 28 April 2014
- import platform >>> import vistrails as vt42 KB (6,625 words) - 13:59, 26 May 2017
- * [RR] Export/import workflow to Python working! ** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit work39 KB (5,418 words) - 21:13, 30 August 2016
- import os12 KB (1,604 words) - 14:25, 22 April 2012
- import os18 KB (2,508 words) - 22:55, 4 December 2007
- ** '''[https://www.vistrails.org/ticket/762 762](tbm)''' import sys package ** replace import statement to add "vistrails." prefix70 KB (10,493 words) - 15:04, 4 August 2014
- *** allow users to import aliases, but don't write back to vistrail unless users wants to ** Import vistrail from DB is now very fast.35 KB (5,303 words) - 18:30, 18 December 2013
- import os19 KB (2,647 words) - 00:07, 12 December 2008
- ** e.g. "import core.vistrail.module" becomes "import vistrails.core.vistrail.module" ** Also, for "import vistrails" style use of VisTrails, it would be nice to be able to specify w52 KB (8,076 words) - 18:34, 18 December 2013
- *** Updates print to functions 'from __future__ import print_function' *** Fixes relative imports (from __future__ import absolute_import)36 KB (5,008 words) - 15:34, 30 October 2017
- ** Add higher-level features like "Upgrade All" for (1), "Import Changes to My Subworkflows", etc. ...figuration widgets not as classes but rather some text that can be used to import the GUI elements only when using the GUI code. However, what would happen35 KB (5,731 words) - 18:36, 18 December 2013
- *** When loading, ask 'Do you want to import package in bundle' if not already existing. ** [TE] import data into vistrails?, truncate based on a map from file locations to bundle69 KB (10,097 words) - 15:20, 4 February 2015