semvec/pypi-packages huggingface dataset:
web-maya 0.0.7
Mini web-framework package that provides basic web-programming features.

# [Maya](https://github.com/Vladislavus1/Maya)

![Maya Logo](https://static.wikia.nocookie.net/azumanga/images/3/3f/Maya.jpg)

Maya is a lightweight Python package for handling HTTP requests, responses, and server operations. It provides an easy-to-use framework for managing web interactions efficiently.

## Features

- Request handling
- Response generation
- Cookie management
- Simple server setup

## Installation

To install Maya, simply clone the repository and use it in your project:

```bash
# Clone the repository
git clone https://github.com/Vladislavus1/Maya.git
cd maya
```

Alternatively, if this package is published on PyPI:

```bash
pip install web_maya
```

## Usage

Here's a basic example of how to use Maya:

```python
from web_maya import WebServer, render_from_string

app = WebServer()


def home():
    return render_from_string("Hello, world!")


app.add_route('/', home)

if __name__ == "__main__":
    app.run()
```

## Modules Overview

- `maya.request` - Handles HTTP requests.
- `maya.response` - Generates HTTP responses.
- `maya.cookies` - Manages cookies.
- `maya.server` - Runs the web server.

## Contributing

Contributions are welcome! Feel free to open issues or submit pull requests.
mkdocs-gherkin-plugin 0.0.13
An Mkdocs Plugin that Injects Cucumber Results in your Living Documentation
Requires Python: >=3.8

# Mkdocs Gherkin Results Plugin

This plugin parses and injects the results of a Cucumber test report back into your Mkdocs pages.

This allows to create a living documentation where your Cucumber scenarios are written in Gherkin format (see link bellow).

It works by parsing the Cucumber messages, generated during the tests, and injecting the results in the Markdown before it is parsed as HTML, using the **on_page_markdown** hook.


## Features

- Whenever a test case has passed, a checkmark will be added next to it.

  ![images/screenshot1.png](https://github.com/sashokbg/mkdocs-gherkin-plugin/raw/main/images/screenshot_1.png)

- If a test case has failed a cross will be added.

- Screenshot attachments

  ![images/screenshot2.png](https://github.com/sashokbg/mkdocs-gherkin-plugin/raw/main/images/screenshot_2.png)

## Examples

Check the configuration example under _example_ directory.

It configures both cucumber-js and mkdocs in the same directory.

To run the example, you need to:

* Run the cucumber tests

  * cd tests/test-docs
  * npm i
  * npm run test

* Run the mkdocs documentation

  * Create and activate your python venv, using your preferred method
  * Run the documentation generator 

    `python tests/test-docs/run.py`


## Installing

In your mkdocs.yaml add the following:
```yaml
plugins:
- gherkin-plugin
```

## Configuration

- **tests_root_path** - Required. The relative path of where the cucumber tests are located. Example "./tests-e2e"

- **show_results** - Boolean value that controls if the test results are shown next to each feature and step. Defaults to True

- **show_attachments** - Boolean value that controls if the file attachements are shown in the final result. Defaults to True

- **messages_path** - Location where to load the cucumber messages ndjson. Defaults to "gherkin_messages.ndjson"

Example:
```yaml
plugins:
  show_attachments: True
  messages_path: "gherkin_messages.ndjson"
```

### Dependencies
If you use screenshots attachments, you will need to add the following markdown dependencies as well:


```yaml
markdown_extensions:
  - admonition
  - pymdownx.details
  - pymdownx.superfences
```

## TODO

- [ ] Fix pending steps not shown
- [ ] Add a short video explaining how it all works

## References

- https://github.com/cucumber/gherkin/blob/main/MARKDOWN_WITH_GHERKIN.md

- https://github.com/cucumber/messages

- https://cucumber.io/blog/podcast/living-documentation/

- https://www.mkdocs.org/dev-guide/plugins/
monaco-2018-report 0.4.2
Processes racing data to generate a detailed report of racer statistics.
Requires Python: >=3.8

# Report of Monaco 2018 Racing

This project processes racing data to generate a detailed report of racer statistics, including race times, rankings,
and team information. It supports sorting results and filtering by specific drivers.


## Features

- **Command-line Interface:** Configure input folder, sorting order, and driver filtering.
- **Data Parsing:** Reads racer data from structured files (`abbreviations.txt`, `start.log`, `end.log`).
- **Time Calculations:** Computes race durations accurately from start and end timestamps.
- **Flexible Reporting:** Displays full rankings or filtered statistics for a single driver.


## Installation
Create and activate a virtual environment:

`virtualenv venv`

`venv/scripts/activate`


Install the package:

`python -m pip install monaco_2018_report`

Import the package:

` import monaco_2018_report`


## Usage
Run the script from the command line with the following options:

`python script.py --folder_path <path_to_data_folder> [--order <asc|desc>] [--driver <driver_name>]`

Arguments:
- --folder_path (required): Path to the folder containing abbreviations.txt, start.log, and end.log.
- --order (optional): Sorting order of the report.
  - Options:
      - asc (default): Ascending order of race times.
      - desc: Descending order of race times.
- --driver (optional): Filter and show statistics for a specific driver.


## Usage Exemple

`python script.py --folder_path ./data --order desc --driver "Fernando Alonso"`

## Output
- **Ranked Report:** Displays all racers, sorted by race time, with a separator distinguishing the top 15 racers.
- **Driver Statistics:** Shows details of a specific driver's performance if --driver is specified


## File Requirements
The input folder must contain:

- **abbreviations.txt:** Racer abbreviations, names, and team data.
- **start.log:** Start times for each racer.
- **end.log:** End times for each racer.


## Error Handling
- Ensures all required files are present.
- Validates input data formats.
- Provides informative error messages for missing or invalid arguments.