Shared is a place for code that is common to multiple python repositories on codecov.
We believe that everyone should have access to quality software (like Sentry), that’s why we have always offered Codecov for free to open source maintainers.
By making our code public, we’re not only joining the community that’s supported us from the start — but also want to make sure that every developer can contribute to and build on the Codecov experience.
shared is a repository of its own, so it needs to be installed as a dependency on the repositories that might use it.
The current repositories using shared are codecov/worker and codecov/codecov-api.
Whenever getting new code into shared, one needs to wait for a new version to be released (or release it themselves, see below), and update the requirements.in file in codecov/worker and codecov/codecov-api to use the newly released version of shared.
To get started, you will need a few things due the presence of a rust extension on this package:
- Have rust installed in your system
- Have a virtualenv (whichever one you prefer)
- Run
pip install setuptools-rust pip-tools
python setup.py develop
pip install -r requirements.txt -r tests/requirements.txt
To release a new version, you need to:
- Check what the next version should be.
- You can check the latest version on https://github.com/codecov/shared/releases
- As a rule of thumb, just add one to the micro version (number most to the right)
- Create a new PR:
- Changing the
versionfield on https://github.com/codecov/shared/blob/main/setup.py#L12 to that new version - Change https://github.com/codecov/shared/blob/main/CHANGELOG.md unreleased header name to that version, and create a new unreleased section with the same subsections.
- Merge that PR
- Create a new release on https://github.com/codecov/shared/releases/new
In order to run tests, from inside the virtualenv this repo is in:
make test
As a normal python package, shared can include dependencies of its own.
Updating them should be done at the setup.py file.
Remember to add dependencies as loosely as possible. Only make sure to include what the minimum version is, and only include a maximum version if you do know that higher versions will break.
Remember that multiple packages, on different contexts of their own requirements, will have to install this. So keeping the requirements loose allow them to avoid version clashes and eases upgrades whenever they need to.
Rust Service to be called from inside python
This is some rust code that is meant to be installed as a python wheel on the repository and used
It uses pyo3 as the binding and setuptools-rust as the tool that turns the rust code into python
We hope it provides a new level of speed to the CPU-bound parts of the code
This repository, like all of Codecov's repositories, strives to follow our general Contributing guidlines. If you're considering making a contribution to this repository, we encourage review of our Contributing guidelines first.