We'd love to get patches from you!
To compile Pedalboard from scratch, the following packages will need to be installed:
- Python 3.8 or higher.
- A C++ compiler, e.g.
gcc
,clang
, etc.- On macOS, a working Xcode installation should provide this.
- On Linux:
- FreeType 2 (
libfreetype-dev
,libfreetype2-dev
, orfreetype2-devel
) - X11 (
xorg-dev
should do)
- FreeType 2 (
git clone --recurse-submodules --shallow-submodules git@github.com:spotify/pedalboard.git
cd pedalboard
pip3 install pybind11 tox
pip3 install .
To compile a debug build of pedalboard
that allows using a debugger (like gdb or lldb), use the following command to build the package locally and install a symbolic link for debugging:
python3 setup.py build develop
Then, you can import pedalboard
from Python (or run the tests with tox
) to test out your local changes.
If you're on macOS or Linux, you can try to compile a debug build faster by using Ccache:
brew install ccache rm -rf build && CC="ccache clang" CXX="ccache clang++" DEBUG=1 python3 -j8 -m pip install -e .e.g.
sudo yum install ccache # or apt, if on a Debian # If using GCC: rm -rf build && CC="ccache gcc" CXX="scripts/ccache_g++" DEBUG=1 python3 setup.py build -j8 develop # ...or if using Clang: rm -rf build && CC="ccache clang" CXX="scripts/ccache_clang++" DEBUG=1 python3 setup.py build -j8 develop
By default, all .cpp
and .mm
files in the pedalboard
directory (or subdirectories) will be automatically compiled by setup.py
.
While pedalboard
is mostly C++ code, it ships with .pyi
files to allow for type hints in text editors and via MyPy. To update the type hint files, use the following commands:
# Use pybind11-stubgen to create intermediate stub files:
pybind11-stubgen -o stubs_output pedalboard pedalboard_native --no-setup-py
# Post-process the stub files into more human-readable, usable ones:
python3 -m scripts.postprocess_type_hints stubs_output pedalboard --check
# Run mypy.stubtest to ensure the resulting stubs are valid
python3 -m mypy.stubtest pedalboard --allowlist stubtest.allowlist
# If all looks good, commit the resulting stubs to Git.
We follow the GitHub Flow Workflow:
- Fork the project
- Check out the
master
branch - Create a feature branch
- Write code and tests for your change
- From your branch, make a pull request against
https://github.com/spotify/pedalboard
- Work with repo maintainers to get your change reviewed
- Wait for your change to be pulled into
https://github.com/spotify/pedalboard/master
- Delete your feature branch
We use tox
for testing - running tests from end-to-end should be as simple as:
pip3 install tox
tox
Use clang-format
for C++ code, and black
with defaults for Python code.
When creating an issue please try to ahere to the following format:
module-name: One line summary of the issue (less than 72 characters)
### Expected behaviour
As concisely as possible, describe the expected behaviour.
### Actual behaviour
As concisely as possible, describe the observed behaviour.
### Steps to reproduce the behaviour
List all relevant steps to reproduce the observed behaviour.
Files should be exempt of trailing spaces.
We adhere to a specific format for commit messages. Please write your commit
messages along these guidelines. Please keep the line width no greater than 80
columns (You can use fmt -n -p -w 80
to accomplish this).
module-name: One line description of your change (less than 72 characters)
Problem
Explain the context and why you're making that change. What is the problem
you're trying to solve? In some cases there is not a problem and this can be
thought of being the motivation for your change.
Solution
Describe the modifications you've done.
Result
What will change as a result of your pull request? Note that sometimes this
section is unnecessary because it is self-explanatory based on the solution.
Some important notes regarding the summary line:
- Describe what was done; not the result
- Use the active voice
- Use the present tense
- Capitalize properly
- Do not end in a period — this is a title/subject
- Prefix the subject with its scope
We also welcome improvements to the project documentation or to the existing docs. Please file an issue.
If you are a first time contributor to pedalboard
, familiarize yourself with the:
When you're ready, navigate to issues. Some issues have been identified by community members as good first issues.
There is a lot to learn when making your first contribution. As you gain experience, you will be able to make contributions faster. You can submit an issue using the question label if you encounter challenges.
By contributing your code, you agree to license your contribution under the terms of the LICENSE.
Read our Code of Conduct for the project.
Try updating your version of pip
:
pip install --upgrade pip
You may have networking issues. Check to make sure you do not have the PIP_INDEX_URL
environment variable set (or that it points to a valid index).
Ensure you have the Python development packages installed.
You will need to find correct package for your operating system. (i.e.: python-dev
, python-devel
, etc.)
Ensure that all Git submodules have been updated:
git submodule update --init
- Ensure that you have Tox version 4 or greater installed
- or set
ignore_basepython_conflict=true
intox.ini
- or install Tox using
pip
and not your system package manager