semvec/pypi-packages huggingface dataset:
labscribe 0.4.7
A small package for managing python experiment scripts
Requires Python: >=3

# labscribe
[![PyPI version](https://badge.fury.io/py/labscribe.svg)](https://badge.fury.io/py/labscribe) [![Documentation Status](https://readthedocs.org/projects/labscribe/badge/?version=latest)](https://labscribe.readthedocs.io/en/latest/?badge=latest)

Welcome to labscribe, a python package for the recording of experiments -- logging of assets, metrics/results, and command line parameters. We feature a number of different formats for logging that include CSV files, GoogleSheets and SQLite.

### Getting started

To install labscribe, simply install from pypi:

```bash
pip install --upgrade labscribe
```
gymnasium-notices 0.0.1
Notices for gymnasium

# Gymnasium Notices

This repository hosts notices for Gym that may be displayed on import on internet connected systems, in order to give notices if versions have major reproducibility issues, are very old and need to be upgraded (e.g. there's been issues with researchers using 4 year old versions of Gymnasium for no reason), or other similar issues. If you're using a current version of Gym and nothing extraordinary happens, you'll never see a message from this, but I want start including the option to prevent future issues. By pulling the error messages from a public git repository, there's absolute transparency and versioning in the process.
matrix-common 1.3.0
Common utilities for Synapse, Sydent and Sygnal
Requires Python: >=3.7

# matrix-python-common

Common utilities for Synapse, Sydent and Sygnal.


## Installation

```shell
pip install matrix-common
```


## Usage
```py
import matrix_common
```


## Development

In a virtual environment with pip ≥ 21.1, run
```shell
pip install -e .[dev]
```

To run the unit tests, you can either use:
```shell
tox -e py
```
or
```shell
trial tests
```

To run the linters and `mypy` type checker, use `./scripts-dev/lint.sh`.


## Releasing

The exact steps for releasing will vary; but this is an approach taken by the
Synapse developers (assuming a Unix-like shell):

 1. Set a shell variable to the version you are releasing (this just makes
    subsequent steps easier):
    ```shell
    version=X.Y.Z
    ```

 2. Update `setup.cfg` so that the `version` is correct.

 3. Stage the changed files and commit.
    ```shell
    git add -u
    git commit -m v$version -n
    ```

 4. Push your changes.
    ```shell
    git push
    ```

 5. When ready, create a signed tag for the release:
    ```shell
    git tag -s v$version
    ```
    Base the tag message on the changelog.

 6. Push the tag.
    ```shell
    git push origin tag v$version
    ```

 7. If applicable:
    Create a *release*, based on the tag you just pushed, on GitHub or GitLab.

 8. If applicable:
    Create a source distribution and upload it to PyPI:
    ```shell
    python -m build
    twine upload dist/matrix_common-$version*
    ```