semvec/pypi-packages huggingface dataset:
dongle-core 0.1.0.dev4
Python license manager (core runtime)
Requires Python: >=3.11

<!--
SPDX-FileCopyrightText: 2025 led-inc.eu

SPDX-License-Identifier: CC-BY-SA-4.0
-->

# dongle License Framework

This package provides a framework that can be used to run signed and encrypted Python code.
The protocol is based on public key cryptography and tries to adhere to common standards.

Except for `cryptography`, no third party components are required.
The implementation is compliant with CPython standards and does not require any patched runtime.
django-fbv 0.8.0
Utilities to make function-based views cleaner, more efficient, and better tasting. 
Requires Python: >=3.10
Keywords: django, web, python, django

<p align="center">
  <a href="https://django-fbv.adamghill.com"><h1 align="center">django-fbv</h1></a>
</p>
<p align="center">Utilities to make Django function-based views cleaner, more efficient, and better tasting. 💥</p>

![PyPI](https://img.shields.io/pypi/v/django-fbv?color=blue&style=flat-square)
![PyPI - Downloads](https://img.shields.io/pypi/dm/django-fbv?color=blue&style=flat-square)
![GitHub Sponsors](https://img.shields.io/github/sponsors/adamghill?color=blue&style=flat-square)

📖 Complete documentation: https://django-fbv.adamghill.com

📦 Package located at https://pypi.org/project/django-fbv/

## Features

## Features

### Decorators

- [`fbv.decorators.render_html`](https://django-fbv.adamghill.com/en/latest/decorators/#render-html): renders a view as HTML with the specified template
- [`fbv.decorators.render_view`](https://django-fbv.adamghill.com/en/latest/decorators/#render-view): renders a view as a content type with the specified template
- [`fbv.decorators.render_json`](https://django-fbv.adamghill.com/en/latest/decorators/#render-json): 
renders dictionaries, Django Models, or Django QuerySets as a JSON response

### Views

- [`fbv.views.html_view`](https://django-fbv.adamghill.com/en/latest/views/#html-view): directly render a template from `urls.py`
- [`fbv.views.redirect_view`](https://django-fbv.adamghill.com/en/latest/views/#redirect-view): redirect to a pattern name from `urls.py`
- [`fbv.views.file`](https://django-fbv.adamghill.com/en/latest/views/#file): serve a file
- [`fbv.views.favicon_file`](https://django-fbv.adamghill.com/en/latest/views/#favicon-file): serve an image file as the favicon.ico
- [`fbv.views.favicon_emoji`](https://django-fbv.adamghill.com/en/latest/views/#favicon-emoji): serve an emoji as the favicon.ico

### Middleware

- [`fbv.middleware.RequestMethodMiddleware`](https://django-fbv.adamghill.com/en/latest/middleware/): adds a boolean property to the `request` for the current request's HTTP method

Read all of the documentation at https://django-fbv.adamghill.com/.
bpkit 0.0.7
Blueprint development kit for Python
Requires Python: <4.0,>=3.9
Keywords: python

# bpkit

[![Release](https://img.shields.io/github/v/release/evgnomon/bpkit)](https://img.shields.io/github/v/release/evgnomon/bpkit)
[![Build status](https://img.shields.io/github/actions/workflow/status/evgnomon/bpkit/main.yml?branch=main)](https://github.com/evgnomon/bpkit/actions/workflows/main.yml?query=branch%3Amain)
[![codecov](https://codecov.io/gh/evgnomon/bpkit/branch/main/graph/badge.svg)](https://codecov.io/gh/evgnomon/bpkit)
[![Commit activity](https://img.shields.io/github/commit-activity/m/evgnomon/bpkit)](https://img.shields.io/github/commit-activity/m/evgnomon/bpkit)
[![License](https://img.shields.io/github/license/evgnomon/bpkit)](https://img.shields.io/github/license/evgnomon/bpkit)

Blueprint development kit for Python

- **Github repository**: <https://github.com/evgnomon/bpkit/>
- **Documentation** <https://evgnomon.github.io/bpkit/>

## Getting started with your project

### 1. Create a New Repository

First, create a repository on GitHub with the same name as this project, and then run the following commands:

```bash
git init -b main
git add .
git commit -m "init commit"
git remote add origin git@github.com:evgnomon/bpkit.git
git push -u origin main
```

### 2. Set Up Your Development Environment

Then, install the environment and the pre-commit hooks with

```bash
make install
```

This will also generate your `uv.lock` file

### 3. Run the pre-commit hooks

Initially, the CI/CD pipeline might be failing due to formatting issues. To resolve those run:

```bash
uv run pre-commit run -a
```

### 4. Commit the changes

Lastly, commit the changes made by the two steps above to your repository.

```bash
git add .
git commit -m 'Fix formatting issues'
git push origin main
```

You are now ready to start development on your project!
The CI/CD pipeline will be triggered when you open a pull request, merge to main, or when you create a new release.

To finalize the set-up for publishing to PyPI, see [here](https://fpgmaas.github.io/cookiecutter-uv/features/publishing/#set-up-for-pypi).
For activating the automatic documentation with MkDocs, see [here](https://fpgmaas.github.io/cookiecutter-uv/features/mkdocs/#enabling-the-documentation-on-github).
To enable the code coverage reports, see [here](https://fpgmaas.github.io/cookiecutter-uv/features/codecov/).

## Releasing a new version

- Create an API Token on [PyPI](https://pypi.org/).
- Add the API Token to your projects secrets with the name `PYPI_TOKEN` by visiting [this page](https://github.com/evgnomon/bpkit/settings/secrets/actions/new).
- Create a [new release](https://github.com/evgnomon/bpkit/releases/new) on Github.
- Create a new tag in the form `*.*.*`.

For more details, see [here](https://fpgmaas.github.io/cookiecutter-uv/features/cicd/#how-to-trigger-a-release).

---

Repository initiated with [fpgmaas/cookiecutter-uv](https://github.com/fpgmaas/cookiecutter-uv).