Open mbrochh opened 9 years ago
It will use the default virtualenv
@mbrochh did you make any progress with this? I'd like to know if you found a way to do what you want. Ideally we would support your use-case, but it might require that we provide the ability to specify some environment variables or you modify the shebang line.
I tried adding the shebang
#!/usr/bin/env python
to a simple Python script. The script imports something that is only available in a virtualenv. I had that virtualenv active then I started atom but when I run the script, it fails and says that it can't find that imported module.I could of course point the shebang exactly at the exeutable in my virtualenv but that doesn't sound like the correct way to do things since every developer would have different paths.
Any idea how I can get
#!/usr/bin/env python
playing nicely with script-runner?