semvec/pypi-packages huggingface dataset:
certbot-dns-hotline 0.4.0
Certbot DNS plugin for Hotline
License: MIT
Requires Python: >=3.6

# certbot-dns-hotline
Certbot DNS plugin for Hotline

Based on https://github.com/schleuss/certbot_dns_freedns and https://github.com/m42e/certbot-dns-ispconfig

This is used in conjunction with [Hotline](https://github.com/captainGeech42/hotline) for issuing SSL certificates for the callback domain.

## Usage

Change the domains to match your callback domain, along with the `--dns-hotline-path` to the directory shared with the DNS callback service

```
$ certbot certonly \
    --authenticator dns-hotline \
    --dns-hotline-path /hotline/acme \
    --server https://acme-v02.api.letsencrypt.org/directory \
    --agree-tos \
    --rsa-key-size 4096 \
    -d 'hotlinecallback.net' \
    -d '*.hotlinecallback.net'
```
pytest-execution-timer 0.1.0
A timer for the phases of Pytest's execution.
License: MIT
Requires Python: >=3.7,<4.0

# pytest-execution-timer

A plugin to use with Pytest to measure execution time of tests.

Distinctly different from the `--durations` option of pytest,
this plugin measures specific pytest startup/collection phases.

Leverages `pytest` hooks to measure execution time of phases.

---

## Installation

Requires:

- Python 3.7 or later.
- Pytest 6.2 or later.

Install the plugin with any approach for your project.

Some examples:

```shell
pip install pytest-execution-timer
```

```shell
poetry add --dev pytest-execution-timer
```

```shell
pipenv install --dev pytest-execution-timer
```

Or add it to your `requirements.txt` file.

## Usage

Enable the plugin with the `--execution-timer` option when running `pytest`:

```console
$ pytest --execution-timer
...
Durations of pytest phases in seconds (min 100ms):
0.662	pytest_runtestloop
```

Control the threshold (default 100ms) by passing `--minimum-duration=<value in ms>`:

```console
$ pytest --execution-timer --minimum-duration=1000  # 1 second
```

## Understanding the output

The best ay to start is to compare the difference of the `pytest_runtestloop` duration
and the overall duration of the test run. Example:

```console
Durations of pytest phases in seconds (min 100ms):
0.666	pytest_runtestloop
====== 4 passed in 0.68s ======
```

In this example, there's not much lost between the test run and the `pytest_runtestloop`
meaning that the startup and collection phases are not taking too much time.

If there's a larger difference in the timings,
look to other emitted phases to understand what's taking the most time.

These can then be examined directly,
or use other tools like [profilers](https://docs.python.org/3/library/profile.html)
or [import timings](https://docs.python.org/3/using/cmdline.html#cmdoption-X).

## License

Distributed under the terms of the MIT license,
"pytest-execution-timer" is free and open source software.
See `LICENSE` for more information.