semvec/pypi-packages huggingface dataset:
borco-scikit-build-core-example 0.0.5
Example package using scikit-build-core and Qt6
Requires Python: >=3.12

# scikit-build-code example

A simple project to build a python module using
[scikit-build-core](https://scikit-build-core.readthedocs.io/en/latest/) and Qt6.

## Code Organization

Folder | Notes
---|---
src/cpp/_core_lib | main code (as a library)
src/cpp/_core | pybind11 bindings
src/example | wrapps the pybind11 bindings adds typing info and docstrings to it
tests/cpp/catch | C++ tests using [Catch2](https://github.com/catchorg/Catch2)
tests/cpp/google | C++ tests using [Google Test](https://google.github.io/googletest/)
tests/cpp/qtest | C++ tests using [QtTest](https://doc.qt.io/qt-6/qttest-index.html)
tests/python | Python tests

## C++ development

* load the main `CMakeLists.txt` in `QtCreator` or open the code folder in `VSCode`

## C++ tests

* load the main `CMakeLists.txt` in `QtCreator`
* run all test with `Tools > Tests > Run All Tests` (`Alt+Shift+T, Alt+A`)
* check the results in the `Test Results` dock (`Alt+9`)

### Catch2

Disabled [Catch2](https://github.com/catchorg/Catch2) tests by default because they:

* add a lot of files to the build, increasing the build time
* don't integrate very well with the VSCode test explorer

## Python pybind11 bindings

* the binding library is located in `src/cpp/_core`
* the `src/cpp/example` contains a wrapper for the binding library that adds some typing
  info and some docstrings
* the `tests/python` folder has some `pytest` tests using the `example` package

### Building pybind11 bindings

The `_core_lib` library that provides the main functionality is built with Qt6. For this
reason, `cmake` must find it. The easiest way to solve this is to:

* install Qt6
* define `Qt6_DIR` environment variable

This example defines the `Qt6_DIR` in the `.vscode/settings.json` file where local
`VSCode` workspace configuration is defined.

```js
{
    "cmake.buildDirectory": "${workspaceFolder}/build/vscode",
    "cmake.generator": "Ninja",
    "terminal.integrated.env.windows": {
        "Qt6_DIR": "C:/Qt/6.8.1/msvc2022_64",
    }
}
```

Once Qt6 is installed and `Qt6_DIR` is set, open the project in `VSCode` and run this
command:

```bash
uv sync
```

After the initial sync, the tests can be run with:

```bash
uv run pytest
```
ryser 0.2.0
Latin squares and related designs.
Requires Python: <4.0,>=3.10

[![PyPI version](https://badge.fury.io/py/ryser.svg)](https://badge.fury.io/py/ryser)
![python package](https://github.com/MHenderson/ryser/actions/workflows/python-package.yml/badge.svg)
![python publish](https://github.com/MHenderson/ryser/actions/workflows/python-publish.yml/badge.svg)

# ryser
 
Latin squares and related designs
borco_scikit_build_core_example 0.0.4
Example package using scikit-build-core and Qt6
Requires Python: >=3.12

# scikit-build-code example

A simple project to build a python module using
[scikit-build-core](https://scikit-build-core.readthedocs.io/en/latest/) and Qt6.

## Code Organization

Folder | Notes
---|---
src/cpp/_core_lib | main code (as a library)
src/cpp/_core | pybind11 bindings
src/example | wrapps the pybind11 bindings adds typing info and docstrings to it
tests/cpp/catch | C++ tests using [Catch2](https://github.com/catchorg/Catch2)
tests/cpp/google | C++ tests using [Google Test](https://google.github.io/googletest/)
tests/cpp/qtest | C++ tests using [QtTest](https://doc.qt.io/qt-6/qttest-index.html)
tests/python | Python tests

## C++ development

* load the main `CMakeLists.txt` in `QtCreator` or open the code folder in `VSCode`

## C++ tests

* load the main `CMakeLists.txt` in `QtCreator`
* run all test with `Tools > Tests > Run All Tests` (`Alt+Shift+T, Alt+A`)
* check the results in the `Test Results` dock (`Alt+9`)

### Catch2

Disabled [Catch2](https://github.com/catchorg/Catch2) tests by default because they:

* add a lot of files to the build, increasing the build time
* don't integrate very well with the VSCode test explorer

## Python pybind11 bindings

* the binding library is located in `src/cpp/_core`
* the `src/cpp/example` contains a wrapper for the binding library that adds some typing
  info and some docstrings
* the `tests/python` folder has some `pytest` tests using the `example` package

### Building pybind11 bindings

The `_core_lib` library that provides the main functionality is built with Qt6. For this
reason, `cmake` must find it. The easiest way to solve this is to:

* install Qt6
* define `Qt6_DIR` environment variable

This example defines the `Qt6_DIR` in the `.vscode/settings.json` file where local
`VSCode` workspace configuration is defined.

```js
{
    "cmake.buildDirectory": "${workspaceFolder}/build/vscode",
    "cmake.generator": "Ninja",
    "terminal.integrated.env.windows": {
        "Qt6_DIR": "C:/Qt/6.8.1/msvc2022_64",
    }
}
```

Once Qt6 is installed and `Qt6_DIR` is set, open the project in `VSCode` and run this
command:

```bash
uv sync
```

After the initial sync, the tests can be run with:

```bash
uv run pytest
```
beku-stackabletech 0.0.11rc1
Test suite expander for Stackable Kuttl tests.
Requires Python: >=3.7

# beku

Version: 0.0.11-rc1

Fast [Kuttl](https://kuttl.dev/) tests expander for Stackable integration tests.

```sh
beku -i tests/test-definition.yaml -t tests/templates/kuttl -k tests/kuttl-test.yaml.jinja2 -o tests/_work
```

`beku` parses a test definition YAML file together with a directory of templated Kuttl test definitions.
From this it generates Kuttl test suites which can then be run with plain Kuttl.
This was built on top of Kuttl to support running tests with different version combinations of products, or slightly different features enabled,
without having to duplicate tests.

## Installation

We recommend to use [pipx](https://pypa.github.io/pipx/):

```sh
pipx install beku-stackabletech
```

But you can also use `pip`:

```sh
# from PyPI
pip install beku-stackabletech
# from GitHub
pip install git+https://github.com/stackabletech/beku.py.git@main
```

Or via NixOS and Nix Shell:

```nix
{ lib, pkgs, ... }:
with lib;
let
  beku = pkgs.callPackage(pkgs.fetchFromGitHub {
    owner = "stackabletech";
    repo = "beku.py";
    rev = "145e8210f5786b8128e3af43f60b61f065cc2c39";
    hash = "sha256-hLaIY4BE+VIMeKmS3JLOZy87OC2VuQtbX/NCIbQr2p4="; # use lib.fakeHash to find new hashes when upgrading
  } + "/beku.nix") {};
in
{
  packages = with pkgs; [
    beku
    # ...
  ];

  // ...
}
```

## Usage

```sh
cd <stackable operator directory>
rm -rf tests/_work && beku
cd tests/_work && kubectl kuttl test
```

Also see the `examples` folder.

## Release a new version

Update the version in:

* `src/beku/version.py`
* `README.md` : version and pip install command.

Update the CHANGELOG.
Commit and tag.
Build and publish:

```sh
rm -rf dist/
python -m build --sdist --wheel .
twine upload dist/*
```
streamlit-monaco-code-editor 0.0.4
A wrapper of the Monaco Editor for Streamlit
Requires Python: >=3.7

# Streamlit Manoco Code Editor

![PyPI - Version](https://img.shields.io/pypi/v/streamlit-monaco-code-editor)

## Installation

```sh
pip install streamlit-monaco-code-editor
```


A wrapper of the Monaco Code Editor for Streamlit

- Support dynamic height and min height.
- Switch `vs-dark` and `vs-light` themes based on Streamlit theme.
- If Dragging a file to the editor, it will read the file content and display it.

![screenshot](screenshot.png)

## Quick start

```sh
cd streamlit_monaco_code_editor/frontend
npm install
npm run start
```

```sh
pip install -e .
```

Test the example:

```sh
streamlit run streamlit_monaco_code_editor/example.py
```