Re: [galaxy-dev] ImportError: No module named galaxy

2011-11-07 Thread Nate Coraor
On Nov 2, 2011, at 4:45 PM, Oren Livne wrote: > Dear Nate, > My PYTHONPATH is already set to this value. Hi Oren, Is it exported? If it's set to Galaxy's lib directory, it should not be possible that the galaxy module can't be found. --nate > Best, > Oren > ___

Re: [galaxy-dev] ImportError: No module named galaxy

2011-11-03 Thread Oren Livne
Dear Nate, My PYTHONPATH is already set to this value. Best, Oren ___ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:

Re: [galaxy-dev] ImportError: No module named galaxy

2011-11-02 Thread Nate Coraor
Oren Livne wrote: > Dear All, > > I am running the example_watcher_folder.py API script and it > intermittently fails to run a workflow on a file dropped into the > import directory (the file is imported and the workflow starts > running, but its jobs hang or fail). Galaxy uses a condor dramaa job

[galaxy-dev] ImportError: No module named galaxy

2011-10-31 Thread Oren Livne
Dear All, I am running the example_watcher_folder.py API script and it intermittently fails to run a workflow on a file dropped into the import directory (the file is imported and the workflow starts running, but its jobs hang or fail). Galaxy uses a condor dramaa job runner. When I look at t