semvec/pypi-packages huggingface dataset:
keeps 0.0.1
Test project
Requires Python: >=3.8,<=3.11

# clitools

[![Release](https://img.shields.io/github/v/release/fpgmaas/clitools)](https://img.shields.io/github/v/release/fpgmaas/clitools)
[![Build status](https://img.shields.io/github/workflow/status/fpgmaas/clitools/Main/main)](https://github.com/fpgmaas/clitools/actions/workflows/main.yml?query=branch%3Amain)
[![codecov](https://codecov.io/gh/fpgmaas/clitools/branch/main/graph/badge.svg)](https://codecov.io/gh/fpgmaas/clitools)
[![Commit activity](https://img.shields.io/github/commit-activity/m/fpgmaas/clitools)](https://img.shields.io/github/commit-activity/m/fpgmaas/clitools)
[![License](https://img.shields.io/github/license/fpgmaas/clitools)](https://img.shields.io/github/license/fpgmaas/clitools)

Test project

- **Github repository**: <https://github.com/fpgmaas/clitools/>
- **Documentation** <https://fpgmaas.github.io/clitools/>

## Getting started with your project

First, create a repository on GitHub with the same name as this project, and then run the following commands:

``` bash
git init -b main
git add .
git commit -m "init commit"
git remote add origin git@github.com:fpgmaas/clitools.git
git push -u origin main
```

Finally, install the environment and the pre-commit hooks with 

```bash
make install
```

You are now ready to start development on your project! The CI/CD
pipeline will be triggered when you open a pull request, merge to main,
or when you create a new release.

To finalize the set-up for publishing to PyPi or Artifactory, see
[here](https://fpgmaas.github.io/clitools/features/publishing/#set-up-for-pypi).
For activating the automatic documentation with MkDocs, see
[here](https://fpgmaas.github.io/clitools/features/mkdocs/#enabling-the-documentation-on-github).
To enable the code coverage reports, see [here](https://fpgmaas.github.io/clitools/features/codecov/).

## Releasing a new version



---

Repository initiated with [fpgmaas/clitools](https://github.com/fpgmaas/clitools).
maybedata 0.8
A Python implementation of a Maybe type that represents potentially missing values
Requires Python: >=3.10

# maybedata

This is a package that implements a Maybe data type in Python that represents values that might or might not exist.

It is implemented as a class hierarchy with an abstract base class `Maybe`. This class is not constructible, but can be called to construct members of its subclasses, `Just` and `Nothing`.

All methods are documented, feel free to call `help()` on the classes!

Call `Maybe(value)` or `Just(value)` to create a value that is present.

Call `Maybe()` or `Nothing()` to create a missing value.

Check `maybe.present` to find out if a value is present.

Access `maybe.value` to get the value if it is present.

Call `maybe.assume_present()` to raise an exception if the value is not present.

Call `maybe.get(default)` to get the value or a default value.

`Maybe` and `Just` are generic classes if you use type hinting.

`Just` and `Nothing` support pattern matching.

`Maybe`, `Just`, and `Nothing` support `len()`, `bool()`, `hash()`, `iter()`, `in`, and `==`.

The method `maybe.alternatively()` can be expressed using `|`.

The method `maybe.then()` can be expressed using `>>`.
carrotinabox 0.0.1
Test project
Requires Python: >=3.8,<=3.11

# clitools

[![Release](https://img.shields.io/github/v/release/fpgmaas/clitools)](https://img.shields.io/github/v/release/fpgmaas/clitools)
[![Build status](https://img.shields.io/github/workflow/status/fpgmaas/clitools/Main/main)](https://github.com/fpgmaas/clitools/actions/workflows/main.yml?query=branch%3Amain)
[![codecov](https://codecov.io/gh/fpgmaas/clitools/branch/main/graph/badge.svg)](https://codecov.io/gh/fpgmaas/clitools)
[![Commit activity](https://img.shields.io/github/commit-activity/m/fpgmaas/clitools)](https://img.shields.io/github/commit-activity/m/fpgmaas/clitools)
[![License](https://img.shields.io/github/license/fpgmaas/clitools)](https://img.shields.io/github/license/fpgmaas/clitools)

Test project

- **Github repository**: <https://github.com/fpgmaas/clitools/>
- **Documentation** <https://fpgmaas.github.io/clitools/>

## Getting started with your project

First, create a repository on GitHub with the same name as this project, and then run the following commands:

``` bash
git init -b main
git add .
git commit -m "init commit"
git remote add origin git@github.com:fpgmaas/clitools.git
git push -u origin main
```

Finally, install the environment and the pre-commit hooks with 

```bash
make install
```

You are now ready to start development on your project! The CI/CD
pipeline will be triggered when you open a pull request, merge to main,
or when you create a new release.

To finalize the set-up for publishing to PyPi or Artifactory, see
[here](https://fpgmaas.github.io/clitools/features/publishing/#set-up-for-pypi).
For activating the automatic documentation with MkDocs, see
[here](https://fpgmaas.github.io/clitools/features/mkdocs/#enabling-the-documentation-on-github).
To enable the code coverage reports, see [here](https://fpgmaas.github.io/clitools/features/codecov/).

## Releasing a new version



---

Repository initiated with [fpgmaas/clitools](https://github.com/fpgmaas/clitools).