This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
The following tools are required to work on debugpy:
- At least one version of Python 3
- Python 2.7 (to run tests)
- Flake8
- Black
- tox
We recommend using Visual Studio Code with the (Python extension)[https://marketplace.visualstudio.com/items?itemName=ms-python.python] to work on debugpy, but it's not a requirement. A workspace file, [debugpy.code-workspace], is provided for the convenience of VSCode users, and sets it up to use the other tools listed above properly.
Tools that are Python packages should be installed via pip corresponding to the Python 3 installation. On Windows:
...> py -m pip install black flake8 tox
On Linux or macOS:
...$ python3 -m pip install black flake8 tox
We use Flake8 for linting. It should be run from the root of the repository, where .flake8 with project-specific linting settings is located. On Windows:
...\debugpy> py -m flake8
On Linux or macOS:
.../debugpy$ python3 -m flake8
We use Black for formatting. All new code files, and all code files that were edited, should be reformatted before submitting a PR. On Windows:
...\debugpy> py -m black
On Linux or macOS:
.../debugpy$ python3 -m black
We use tox to run tests in an isolated environment. This ensures that debugpy is first built as a package, and tox also takes care of installing all the test prerequisites into the environment. On Windows:
...\debugpy> py -m tox
On Linux or macOS:
.../debugpy$ python3 -m tox
This will perform a full run with the default settings. A full run will run tests on Python 2.7 and 3.5-3.8, and requires all of those to be installed. If some versions are missing, or it is desired to skip them for a particular run, tox can be directed to only run tests on specific versions with -e. In addition, the --developer option can be used to skip the packaging step, running tests directly against the source code in src/debugpy. This should only be used when iterating on the code, and a proper run should be performed before submitting a PR. On Windows:
...\debugpy> py -m tox -e py27,py37 --develop
On Linux or macOS:
.../debugpy$ python3 -m tox -e py27,py37 --develop
While tox is the recommended way to run the test suite, pytest can also be invoked directly from the root of the repository. This requires packages in tests/test_requirements.txt to be installed first.
To test integration between debugpy and Visual Studio Code, the latter can be directed to use a custom version of debugpy in lieu of the one bundled with the Python extension. This is done by specifying "debugAdapterPath" in launch.json - it must point at the root directory of the package, which is src/debugpy inside the repository:
{
"type": "python",
"debugAdapterPath": ".../debugpy/src/debugpy/adapter",
...
}