semvec/pypi-packages huggingface dataset:
pytest-schedule 0.0.8
Automate and customize test scheduling effortlessly on local machines.
License: MIT
Requires Python: >=3.8
Keywords: pytest, schedule, automation, parallel, concurrent, tests, test

#### pytest-schedule

**Automate and customize test scheduling effortlessly on local machines.**

### Installation

To install pytest-schedule, use the following command:

```bash
pip install pytest-schedule
```

Make sure you have pytest installed as well:

```bash
pip install pytest
```

<hr>

### Usage

#### Generate a Test Tree

To recursively generate a JSON tree of test module names from the root directory, use:

```bash
python -m pytest_schedule.generate schedule_json
```

This will create a file named `schedule.json` in the root directory.

<hr>

#### Run Tests with Custom Tags

Execute tests with specific tags as defined in `pytest_schedule.json`.

#### Examples:

```bash
python -m pytest_schedule -t <tag>
python -m pytest_schedule --tags smoke,unittest,integration
python -m pytest_schedule --tag unittest --test_module unittest
python -m pytest_schedule --tag unittest --test_module pytest
```

#### Schedule Test Execution Times

To set specific test execution times, modify pytest_schedule.json following this structure:

```json
{
  "0.0.7": [
    {
      "smoke": [
        {
          "test_binary_tree_0.py": "10:15:00"
        }
      ]
    },
    {
      "smoke": [
        {
          "test_module_binary_tree_1_0.py": "10:10:00"
        }
      ]
    },
    {
      "tag": [
        {
          "test_module_binary_tree_2_0_0.py": "00:00:00"
        }
      ]
    }
  ]
}
```

<hr>

#### Command Options

To see all available options, run:

```bash
python -m pytest_schedule --help
```

<hr>

### Logging

Stdout logs are generated in the following format:

```text
[10:49:35] | PYTEST-SCHEDULE |  The job process started.
[10:49:35] | PYTEST-SCHEDULE |   (1) tag::test_a.py::11:50:00 task waiting ..
[10:50:00] | PYTEST-SCHEDULE |   (1) tag::test_a.py::11:50:00 task started ..
[10:50:00] | PYTEST-SCHEDULE |   (1) tag::test_a.py::11:50:00 task completed   [FAILED]
[10:50:00] | PYTEST-SCHEDULE |  The job process finished.
```

The log file is generated in the root directory with the name `pytest_schedule.log`.
mlflow-custom-headers-plugin 1.0.2
MLFlow plugin that allows adding extra headers to requests to MLFlow in order to enable authentication and other use-cases.
License: MIT
Requires Python: >=3.9

# MLFlow Custom Headers Plugin

> [Source code](https://github.com/yakkomajuri/mlflow_custom_headers_plugin)

A package that enables setting any number of custom headers to be passed along with requests to the MLFlow tracking server.

This is very useful for enabling proper authentication on your MLFlow instance beyond MLFlow's simplistic authentication capabilities using basic auth or one single token.

This plugin was inspired by the [mlflow-cloudflare-header-plugin](https://pypi.org/project/mlflow-cloudflare-header-plugin/) and does also provide support for using Cloudflare Access service tokens for securing your MLFlow tracking server.

## Usage

Install the plugin in your project using MLFlow:

```bash
pip install mlflow-custom-headers-plugin
```

Set all the headers you'd like passed in an environment variable called `MLFLOW_CUSTOM_HEADERS`. Key-value header pairs should be separated by commas, and header name and value should be separated by a colon (`:`) without any empty space.

```
export MLFLOW_CUSTOM_HEADERS=Header1:<Header1Value>,Header2:<Header2Value>,Header3:<Header2Value>
```

Example (using Cloudflare Access):

```
export MLFLOW_CUSTOM_HEADERS=CF-Access-Client-Id:<cf_client_id>,CF-Access-Client-Secret:<cf_client_secret>
```
vidimera 0.3.1
Python signature and behaviour checker inspired by Elixir.
License: MIT
Keywords: [signature, behaviour]

# Vidimera

![PyPI](https://img.shields.io/pypi/v/vidimera)
![PyPI - Python Version](https://img.shields.io/pypi/pyversions/vidimera)
![PyPI - Status](https://img.shields.io/pypi/status/vidimera)
![PyPI - License](https://img.shields.io/pypi/l/vidimera)
[![Python package](https://github.com/DevL/vidimera/actions/workflows/python-package.yml/badge.svg)](https://github.com/DevL/vidimera/actions/workflows/python-package.yml)

_Python signature and behaviour checker inspired by Elixir._

In Swedish, _vidimera_ means _to attest_ or _to certify_. It is commonly used to attest that a copy of a document is accurate compared to the original.

## Installation

Install the package `vidimera` version `0.3+` from PyPI.
The recommended `requirements.txt` line is `vidimera~=0.3`.

## Current Functionality

### `assert_implements(object, expected, scope=Behaviour.PUBLIC_AND_SPECIAL)`
- Raises an `AssertionError` listing missing callables and their signatures if there are any. Based on `behaviour.implements`.

### `Behaviour(object)`
- Creates a new `Behaviour` instance.
- If `object` already is an instance of `Behaviour`, it is returned unchanged.

### `behaviour.implemented_by(other, scope=Behaviour.PUBLIC_AND_SPECIAL)`
- Verifies that `other` at least has the same public and dunderscore callables with the same signatures as the `behaviour`.
- Creats a `Behaviour` from `other` before making the comparison.

### `behaviour.implements(other, scope=Behaviour.PUBLIC_AND_SPECIAL)`
- Verifies that the `behaviour` at least has the same public and dunderscore callables with the same signatures as `other`.
- Creats a `Behaviour` from `other` before making the comparison.

### `behaviour.signatures(scope=Behaviour.PUBLIC_AND_SPECIAL)`
- Returns a `set` of tuples that represent the name and the callable selected based on the `scope`.
- Possible scopes include `PUBLIC`, `PRIVATE`, `SPECIAL`, and `PUBLIC_AND_SPECIAL`.

### `MissingBehaviour(delta)`
- An internal representation of missing behaviour. Created from a set of names and signatures. If the set is empty, this object will be truthy. If the set is non-empty, this object is falsy.