Lux is a project undergoing active development. If you are interested in contributing to Lux, the open tasks on GitHub issues, esp. issues labelled with the tag easy, are good places for newcomers to contribute. This guide contains information on the workflow for contributing to the Lux codebase. For more information on the Lux architecture, see this documentation page.
To setup Lux manually for development purposes, you should fork the Github repo and clone the forked version.
git clone https://github.com/USERNAME/lux.gitYou can install Lux by building from the source code in your fork directly:
cd lux/
pip install --user -r requirements.txt
pip install --user -r requirements-dev.txt
python setup.py installWhen you make a change to the source code in the lux/ folder, you can rebuild by doing this:
python setup.py installIt is often useful to test your code changes via Jupyter notebook. To debug your code changes, you can import a "local" copy of Lux without having to rebuild the changes everytime.
For example, you can have a test notebook test.ipynb that imports. Note that when you do import lux at this path, it imports the local lux/ module instead of your global installation (either system-wide or in your virtual environment).
lux/
- test.ipynb
- lux/
In order to keep our codebase clean and readible, we are using PEP8 guidelines. To help us maintain and check code style, we are using black. Simply run black . before commiting. Without running black, the checks on the continuous integration tests can fail. black should be installed for you as part of requirements-dev.
There is a suite of test files for ensuring that Lux is working correctly. These tests are triggered to run via Travis CI whenever there is a commit made to the lux repository. You can run them locally to make sure that your changes are working and do not break any of the existing tests.
To run all the tests, including checking for code formatting, run:
make test
To run a single test file, run:
python -m pytest tests/<test_file_name>.py
You can commit your code and push to your forked repo. Once all of your local changes have been tested and formatted, you are ready to submit a PR. For Lux, we use the "Squash and Merge" strategy to merge in PR, which means that even if you make a lot of small commits in your PR, they will all get squashed into a single commit associated with the PR. Please make sure that comments and unnecessary file changes are not committed as part of the PR by looking at the "File Changes" diff view on the pull request page.
Once the pull request is submitted, the maintainer will get notified and review your pull request. They may ask for additional changes or comment on the PR. You can always make updates to your pull request after submitting it.
Lux uses Sphinx to generate the documentations, which contains both the docstring and the written documentation in the doc/ folder. To build the documentation in HTML, you can run this command locally in the doc/ folder:
make htmlThis generates all the HTML documentation files in doc/_build/html/. The configuration file conf.py contains information related to Sphinx settings. The Sphinx documentations are written as ReStructuredText (*.rst files) and mostly stored in the source/ folder. The documentation inside source/reference is auto-generated by Sphinx. The repository is linked with ReadTheDocs, which triggers the build for the latest documentation based on the most recent commit. As a result, we do not commit anything inside doc/_build in the Github repository.
In order to update the conda recipe on conda forge, you can follow the steps here. The conda recipe needs to be updated when either a new dependency is added or when the version number needs to be updated in the case of a new release.