Welcome to Reqompyler’s documentation!¶

Reqompyler¶

Table of Contents¶

Table of Contents
Description
Installation
Usage
Credits

Description¶

Use pip-tools to compile a requirements.in folder into proper pinned dependencies.

Installation¶

pip install reqompyler

Usage¶

$ reqompyler --help

Usage: reqompyler [OPTIONS]

  Console script for reqompyler.

Options:
  -i, --in PATH      Path to requirements.in folder  [default:
                     ./requirements.in]
  -o, --output PATH  Path to pinned requirements folder  [default:
                     ./requirements]
  --tld PATH         Ideally the top-level-directory of the package (ie, were
                     there is a setup.py). If not None will be used to export
                     a copy of your dev.txt as requirements.txt  [default: .]
  --ignore TEXT      Requirements.in file (without extension) to ignore,
                     if they are required by another they will be used but no dedicated
                     .txt file will be generated.  [default: linting]
  --help             Show this message and exit.

Credits¶

This package was created with Cookiecutter and the zurutech/cookie-monster project template.

Installation¶

Stable release¶

To install Reqompyler, run this command in your terminal:

$ pip install reqompyler

This is the preferred method to install Reqompyler, as it will always install the most recent stable release.

If you don’t have pip installed, this Python installation guide can guide you through the process.

From sources¶

The source for Reqompyler can be downloaded from the GitHub repo.

You can either clone the public repository:

$ git clone https://github.com/zurutech/reqompyler.git

Once you have a copy of the source, you can install it with:

$ cd reqompyler
$ pip install .

Usage¶

To use reqompyler as a CLI tool:

$ reqompyler --help

Usage: reqompyler [OPTIONS]

  Console script for reqompyler.

Options:
  -i, --in PATH      Path to requirements.in folder  [default:
                    ./requirements.in]
  -o, --output PATH  Path to pinned requirements folder  [default:
                    ./requirements]
  --tld PATH         Ideally the top-level-directory of the package (ie, were
                    there is a setup.py). If not None will be used to export
                    a copy of your dev.txt as requirements.txt  [default: .]
  --ignore TEXT      Requirements.in file (without extension) to ignore,
                    if they are required by another they will be used but no dedicated
                    .txt file will be generated.  [default: linting]
  --help             Show this message and exit.

reqompyler¶

Console script for reqompyler.

reqompyler [OPTIONS]

Options

-i, --in <req_in>¶: Path to requirements.in folder [default: ./requirements.in]

-o, --output <req_pinned>¶: Path to pinned requirements folder [default: ./requirements]

--tld <tld>¶: Ideally the top-level-directory of the package (ie, were there is a setup.py). If not None will be used to export a copy of your dev.txt as requirements.txt [default: .]

--ignore <ignore>¶: Requirements.in file (without extension) to ignore,if they are required by another they will be used but no dedicate.txt file will be generated. [default: linting]

Contributing¶

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

You can contribute in many ways:

Types of Contributions¶

Report Bugs¶

Report bugs at https://github.com/zurutech/reqompyler/issues.

If you are reporting a bug, please include:

Your operating system name and version.
Any details about your local setup that might be helpful in troubleshooting.
Detailed steps to reproduce the bug.

Fix Bugs¶

Look through the GitLab issues for bugs. Anything tagged with “bug” and “help wanted” is open to whoever wants to implement it.

Implement Features¶

Look through the GitLab issues for features. Anything tagged with “enhancement” and “help wanted” is open to whoever wants to implement it.

Write Documentation¶

Reqompyler could always use more documentation, whether as part of the official Reqompyler docs, in docstrings, or even on the web in blog posts, articles, and such.

Submit Feedback¶

The best way to send feedback is to file an issue at https://github.com/zurutech/reqompyler/issues.

If you are proposing a feature:

Explain in detail how it would work.
Keep the scope as narrow as possible, to make it easier to implement.
Remember that this is a volunteer-driven project, and that contributions are welcome :)

Get Started!¶

Ready to contribute? Here’s how to set up reqompyler for local development.

Clone reqompyler from the GitHub repository:

$ git clone https://github.com/zurutech/reqompyler.git

Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
```
$ mkvirtualenv reqompyler
$ cd reqompyler/
$ python setup.py develop
```
To get the dev toolchain just pip install the provided requirements into your virtualenv.
```
$ pip install -r requirements/dev.txt
```
Create a branch for local development:
```
$ git checkout -b name-of-your-bugfix-or-feature
```
Now you can make your changes locally.

When you’re done making changes, check that your changes pass flake8, pylint, black and the tests, including testing other Python versions with tox:

Automatically run the pipeline with tox.

   $ tox

**Note:** ``tox`` can be run parallely with ``tox -p auto -o``

Manually run them:

$ pytest -x -s -vvv --doctest-modules reqompyler tests --cov=reqompyler
$ black reqompyler tests
$ isort reqompyler tests
$ flake8 reqompyler tests
$ pylint reqompyler tests

Commit your changes and push your branch to GitLab:

$ git add .
$ git commit -m "Your detailed description of your changes."
$ git push origin name-of-your-bugfix-or-feature

Submit a pull request through the GitLab website.

Pull Request Guidelines¶

Before you submit a pull request, check that it meets these guidelines:

The pull request should include tests.
If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.md.
The pull request should work for the specified Python Versions.
If you have made change to the CI Pipeline test them locally

Tips¶

To run a subset of tests:

$ pytest -x -s -vvv --doctest-modules WHAT_MODULE/TEST_SUBSET_TO_TEST --cov=ashpy

Deploying¶

A reminder for the maintainers on how to deploy. Make sure all your changes are committed (including an entry in HISTORY.md). Then run:

$ bumpversion patch # possible: major / minor / patch
$ git push
$ git push --tags

Travis will then deploy to PyPI if tests pass.

API Reference¶

reqompyler

Top-level package for Reqompyler.

Dependencies Graph¶

Credits¶

Development Lead¶

AI Lab ml@zuru.tech

Contributors¶

None yet. Why not be the first?

Welcome to Reqompyler’s documentation!¶

Reqompyler¶

Table of Contents¶

Description¶

Installation¶

Usage¶

Credits¶

Installation¶

Stable release¶

From sources¶

Usage¶

reqompyler¶

Contributing¶

Types of Contributions¶

Report Bugs¶

Fix Bugs¶

Implement Features¶

Write Documentation¶

Submit Feedback¶

Get Started!¶

Pull Request Guidelines¶

Tips¶

Deploying¶

API Reference¶

Dependencies Graph¶

Credits¶

Development Lead¶

Contributors¶

Indices and tables¶