semvec/pypi-packages huggingface dataset:
pytest-edit 1.2
Edit the source code of a failed test with `pytest --edit`.
License: MIT

# pytest-edit

![PyPI - Version](https://img.shields.io/pypi/v/pytest-edit)
![PyPI - Python Version](https://img.shields.io/pypi/pyversions/pytest-edit)

A simple Pytest plugin for opening editor on the failed tests.

## Installation & usage

Install with:

```
pip install pytest-edit
```

**After installing the plugin, you need to rerun your tests before the plugin
will be able to open them for edition.**

Usage:

```
pytest --edit
```

This will open your `$EDITOR` at the first line of the last failed test. Not
all editors are capable of opening a file at a given line, and not all editors
that do are supported by `pytest-edit`. See below.

You can also specify the test using its index in the shortreport, for example:

```
pytest --edit=2    # will open the third failed test from the last run.
pytest --edit=-2   # will open the second-to-last failed test from the last run.
```

## Setting the right editor & editor support

Use `$EDITOR` environment variable to set the editor that should be opened.
E.g. you can add `export EDITOR=vim` line to your `.bashrc` or `.zshrc` to set
the editor to `vim`.

If no editor is set, the defaults are `vi` for POSIX platforms and `notepad`
for Windows.

The plugin tries to be cleaver about the options given to the detected editor.
If something is not working properly for you, don't hesitate to
[open an issue](https://github.com/MrMino/pytest-edit/issues).

If an editor is not supported, the file of the specified test will be opened
without specifying the line the editor should place the cursor at.

**I have not tested 90% of the editor support** - there are at least 3
platforms with tens of different editors. Issues & PRs welcome.
mtips5s-web-crawling 0.1.5
Setup cực nhanh một môi trường python thông qua lệnh run.sh
License: MIT
Requires Python: >=3.6

chmod +x run.sh&&./run.sh<br />
chmod +x run_report.sh&&./run_report.sh<br />
chmod +x run_git.sh&&./run_git.sh<br />
chmod +x run_pip.sh&&./run_pip.sh<br />
reminder.py 1.0.2
An async Python schedule reminders with custom event triggers on due time.
License: MIT
Requires Python: >=3.8.0

# reminder.py

[![PyPI - Version](https://img.shields.io/pypi/v/reminder.py?color=teal)](https://pypi.org/project/reminder.py)
[![Python Versions](https://img.shields.io/pypi/pyversions/reminder.py?color=teal)](https://pypi.org/project/reminder.py)

A Python library to manage scheduled reminders, events, and callbacks, designed for asynchronous operations.

## Installation

To install **reminder.py**, use the appropriate command for your operating system:

For Windows:

```bash
py -3 -m pip install --upgrade reminder.py
```

For macOS/Linux:

```bash
python3 -m pip install --upgrade reminder.py
```

## Quick Start

Here’s a simple example to get you started with reminder.py:

```python
from reminder import Reminder, Schedule
from datetime import timedelta

reminder = Reminder()

reminder.add_schedule('Task 1: Timer for 1 minute', timedelta(minutes=1))
reminder.add_schedule('Task 2: Reminder in 30 seconds', timedelta(seconds=30), callback='task_reminder')
reminder.add_schedule('Task 3: Another reminder in 30 seconds', timedelta(seconds=30), callback='task_reminder')

@reminder.event
async def on_initiate():
    print(f"Reminder has been initiated")
    
@reminder.event
async def on_schedule(schedule: Schedule):
    print(f"Triggered schedule: {schedule.title}")

@reminder.event
async def on_task_reminder(schedule: Schedule):
    print(f"Custom reminder callback triggered for schedule: {schedule.title}")

reminder.run()

```



## Documentation

For more detailed instructions,
visit the [reminder.py Documentation](https://reminderpy.readthedocs.io/latest/).