Basic requirements and standards
Pull request process:
Fork us on GitHub.
Clone your repository.
Create a feature branch for your issue.
Apply your changes:
Add them, and then commit them to your branch.
Run the tests until they pass.
When you feel you are finished, rebase your commits to ensure a simple and informative commit log.
Create a pull request on GitHub from your forked repository.
Verify that the tests run by Travis-ci are passing.
Syntax and conventions
We use two applications to automatically format the code to save development time. They are both run with pre-commit.
4 spaces, no tabs.
All code should use
flake8 deluge isort -rc -df deluge pylint deluge pylint deluge/plugins/\*/deluge/
Using the pre-commit application can aid in identifying issues while creating git commits.
Strings and bytes
To prevent bugs or errors in the code byte strings (
str) must be decoded to
strings (Unicode text strings,
unicode) on input and then encoded on output.
Classes should follow the Ext coding style.
Class names should be in !CamelCase
Instances of classes should use camelCase.
All relative path separators used within code should be converted to posix format
/, so should not contain
\\. This is to prevent confusion when dealing with cross-platform clients and servers.
All new docstrings must use Napoleon Google Style with old docstrings eventually converted over.
Google Style example:
def func(arg): """Function purpose. Args: arg (type): Description. Returns: type: Description. If the line is too, long indent next line with three spaces. """ return
See complete list of supported headers.
Verify that the documentation parses correctly with:
python setup.py build_docs