Skip to content
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.

Stop running virtualenv-activate within scripts #143

Closed
pb-cdunn opened this issue Jul 23, 2015 · 1 comment · Fixed by #153
Closed

Stop running virtualenv-activate within scripts #143

pb-cdunn opened this issue Jul 23, 2015 · 1 comment · Fixed by #153
Assignees

Comments

@pb-cdunn
Copy link

The environment should be set up before the script starts.

dgordon has had problems using virtualenv (e.g. #137 and #142), so I want to decouple, though we'll still use it within FALCON-integrate.

Not high priority, but I'll get to it eventually, without objection.

@pb-cdunn pb-cdunn self-assigned this Jul 23, 2015
pb-cdunn pushed a commit to pb-cdunn/FALCON that referenced this issue Jul 31, 2015
Instead, expect everything to be available in the environment.
FALCON-integrate/FALCON-make can help set that up.

closes PacificBiosciences#143
@pb-jchin
Copy link
Contributor

pb-jchin commented Aug 1, 2015

@pb-cdunn can you link the corresponded changes in FALCON-integrate for tracking purpose? Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants