Metadata-Version: 2.1
Name: modelon-impact-client
Version: 1.2.0b19
Summary: Client library for easy scripting against Modelon Impact
Home-page: https://www.modelon.com/modelon-impact
License: BSD
Keywords: impact,client,API
Author: WEP
Author-email: impact@modelon.com
Requires-Python: >=3.6.1,<4.0.0
Classifier: License :: Other/Proprietary License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Requires-Dist: requests (>=2.23,<3.0)
Requires-Dist: semantic_version (>=2.8.5,<3.0.0)
Project-URL: Documentation, https://modelon-impact-client.readthedocs.io
Project-URL: Repository, https://github.com/modelon-community/impact-client-python
Description-Content-Type: text/markdown

# Modelon-impact-client
Client library for easy scripting against Modelon Impact

## Installation

For installation instructions and requirements, please refer to the [documentation](https://modelon-impact-client.readthedocs.io).


## Develop

### Creating a shell
Modelon-impact-client is developed using a Docker container for all build tools.
You can get a shell into said container by running:

```
make shell
```

### Manage dependencies
Dependencies are managed by poetry. Add dependencies by running 
`poetry add <package>`  or `poetry add <package> --dev` inside the shell

### Running tests

Tests are executed by running `make test`. You can also run `make test-watch` to get a watcher
that continuously re-runs the tests.

### Running lint
```
make lint
```

## Build

Building chimp is done by running

```
make wheel
```

## Release

The modelon-impact-client build process is a fully automated using `Semantic-release`.

Automation is enabled for:
- Bumping version
- Generate changelog

This is done based on git commit semantics as described here: https://semantic-release.gitbook.io/semantic-release/

To make a new release simply run:
```
make publish
```

This command will detect what branch you are on and your git history and make a appropriate release.

Current configuration can be found in `.releaserc` and specifies that commits to branch `master` should be released and
commits to branch `beta` should be released as a `pre-release`.

This workflow make sure that no administrative time needs to be put into managing the release workflow.

