How To Contribute¶
First off, thank you for considering contributing to
It’s people like you who make it is such a great tool for everyone.
This document is mainly to help you to get started by codifying tribal knowledge and expectations and make it more accessible to everyone. But don’t be afraid to open half-finished PRs and ask questions if something is unclear!
- No contribution is too small! Please submit as many fixes for typos and grammar bloopers as you can!
- Try to limit each pull request to one change only.
- Always add tests and docs for your code. This is a hard rule; patches with missing tests or documentation can’t be accepted.
- Make sure your changes pass our CI. You won’t get any feedback until it’s green unless you ask for it.
- Once you’ve addressed review feedback, make sure to bump the pull request with a short note. Maintainers don’t receive notifications when you push new commits.
- Don’t break backward compatibility.
def func(x): """ Do something. :param str x: A very important parameter. :rtype: str """
If you add or change public APIs, tag the docstring using
.. versionadded:: 16.0.0 WHATor
.. versionchanged:: 17.1.0 WHAT.
Prefer double quotes (
") over single quotes (
') unless the string contains double quotes itself.
Write your asserts as
expected == actualto line them up nicely:
x = f() assert 42 == x.some_attribute assert "foo" == x._a_private_attribute
To run the test suite, all you need is a recent tox. It will ensure the test suite runs with all dependencies against all Python versions just as it will on Travis CI. If you lack some Python versions, you can can always limit the environments like
tox -e py27,py35(in that case you may want to look into pyenv, which makes it very easy to install many different Python versions in parallel).
Write good test docstrings.
This is a sentence. This is another sentence.
If you start a new section, add two blank lines before and one blank line after the header except if two headers follow immediately after each other:
Last line of previous section. Header of New Top Section ------------------------- Header of New Section ^^^^^^^^^^^^^^^^^^^^^ First line of new section.
- Added ``structlog.func()`` that does foo. It's pretty cool. [`#1 <https://github.com/hynek/structlog/pull/1>`_] - ``structlog.func()`` now doesn't crash the Large Hadron Collider anymore. That was a nasty bug! [`#2 <https://github.com/hynek/structlog/pull/2>`_]
Local Development Environment¶
You can (and should) run our test suite using tox however you’ll probably want a more traditional environment too. We highly recommend to develop using the latest Python 3 release because you’re more likely to catch certain bugs earlier.
First create a virtual environment. It’s out of scope for this document to list all the ways to manage virtual environments in Python but if you don’t have already a pet way, take some time to look at tools like pew, virtualfish, and virtualenvwrapper.
Next get an up to date checkout of the
git checkout firstname.lastname@example.org:hynek/structlog.git
Change into the newly created directory and after activating your virtual environment install an editable version of
cd structlog pip install -e .
If you run the virtual environment’s Python and try to
import structlog it should work!
To run the test suite, you’ll need our development dependencies which can be installed using
pip install -r dev-requirements.txt
At this point
python -m pytest
should work and pass!
Again, this list is mainly to help you to get started by codifying tribal knowledge and expectations. If something is unclear, feel free to ask for help!
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. Please report any harm to Hynek Schlawack in any way you find appropriate.
Thank you for considering contributing to