Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems setting up workspace #1392

Closed
lindsve opened this issue Apr 13, 2018 · 1 comment
Closed

Problems setting up workspace #1392

lindsve opened this issue Apr 13, 2018 · 1 comment

Comments

@lindsve
Copy link

lindsve commented Apr 13, 2018

Hi,

I've joined a python project at work and I'm currently trying to set this up in vscode and I'm having some issues doing so.

The project layout is basically as follows:
/projectroot/
/projectroot/env (/bin/python)
/projectroot/doc
/projectroot/docker
/projectroot/loader
/projectroot/loader/tests
/projectroot/webapp
/projectroot/webapp/tests

It is set up with a single virtual environment, but there are two python projects (loader and webapp) in there. If I open vscode within one of the project folders (loader), then I can easily get unit tests discovered and things seem to work. But if I open vscode from the project root folder, then unit tests are no longer discovered.

I'm fairly new to both vscode and python, so it might be some trivial issues here. Would it work better if I set up an isolated virtual environment for each of the two projects?

Environment data

  • VS Code version: 1.22.2
  • Extension version (available under the Extensions sidebar): 2018.3.1
  • OS and version: MacOS X 10.13.4
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6.4
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv

Actual behavior

Unit tests are not discovered

Expected behavior

Unit tests from both python projects are discovered

@lindsve
Copy link
Author

lindsve commented Apr 13, 2018

Seems like I can get this working with multiroot workspaces and multiple virtual environments. Closing this issue for now

@lindsve lindsve closed this as completed Apr 13, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant