semvec/pypi-packages huggingface dataset:
iamdata 0.1.202602211
IAM data for AWS actions, resources, and conditions based on IAM policy documents. Checked for updates daily.
Requires Python: >=3.7

# IAM Data In Python Package

This is a simple package for utilizing AWS IAM data for Services, Actions, Resources, and Condition Keys. Data is embedded in the python package.

New data is checked against the AWS IAM documentation and updated daily if there are changes.

## Installation
```bash
pip install iam-data
```

## Usage
```python
from iamdata import IAMData

iam_data = IAMData()
print(f"Data Version {iam_data.data_version()} updated at {iam_data.data_updated_at()}")
for service_key in iam_data.services.get_service_keys():
    service_name = iam_data.services.get_service_name(service_key)
    print(f"Getting Actions for {service_name}")
    for action in iam_data.actions.get_actions_for_service(service_key):
        action_details = iam_data.actions.get_action_details(service_key, action)
        print(f"{service_key}:{action} => {action_details}")
```

## API
### Services
* `services.get_service_keys()` - Returns a list of all service keys such as 's3', 'ec2', etc.
* `services.get_service_name(service_key)` - Returns the service name for a given service key.
* `services.service_exists(service_key)` - Returns True if the service key exists.

### Actions
* `actions.get_actions_for_service(service_key)` - Returns an array of all actions for a given service key.
* `actions.get_action_details(service_key, action_key)` - Returns an object with the action details such as `description`, `resourceTypes`, and `conditionKeys`.
* `actions.action_exists(service_key, action_key)` - Returns true if the action exists.

### Resources
* `resources.get_resource_types_for_service(service_key)` - Returns an array of all resource types for a given service key.
* `resources.get_resource_type_details(service_key, resource_type_key)` - Returns an object with the resource type details such as `description`, `arnFormat`, and `conditionKeys`.
* `resources.resource_type_exists(service_key, resource_type_key)` - Returns true if the resource type exists.

### Conditions Keys
* `conditions.get_condition_keys_for_service(service_key)` - Returns an array of all condition keys for a given service key.
* `conditions.get_condition_key_details(service_key, condition_key)` - Returns an object with the condition key details such as `description`, `conditionValueTypes`, and `conditionOperators`.
* `conditions.condition_key_exists(service_key, condition_key)` - Returns true if the condition key exists.

### Version Info
The version is number is formatted as `major.minor.updatedAt`. The updatedAt is the date the data was last updated in the format `YYYYMMDDX` where `X` is a counter to enable publishing more than once per day if necessary. For example version `0.1.202408291` has data updated on August 29th, 2024.

The version can be accessed using the `data_version()` method.

There is also `date_updated_at()` which returns the date the data was last updated.
fred-oss 0.66.0
FREDOSS
Requires Python: >=3.12

# FREDOSS

This is the open-source baseline python package called `fred` package by `fred.fahera.mx` (Fahera's Research, Education, and Development Team).

## Installation

```
$ pip install fred-oss
```

By default, the `fred-oss` package will only install the `default` dependencies. You can control which
dependency set to use via the 'dependency tags' via the following pattern:

```
$ pip install 'fred-oss[<tag-1>,<tag-2>,...]'
```

Where `<tag-i>` can be:
* `default`
* `all`
* ...
local-web-services-python-sdk 0.1.1
Python testing SDK for local-web-services — in-process pytest fixtures and boto3 helpers
Requires Python: >=3.11
Keywords: aws, boto3, dynamodb, local, mocking, pytest, s3, sqs, testing

# local-web-services-testing

Python testing SDK for [local-web-services](https://github.com/local-web-services/local-web-services) — in-process pytest fixtures and boto3 helpers for testing AWS applications without needing a running `ldk dev`.

## Installation

```bash
pip install local-web-services-python-sdk
# or
uv add local-web-services-python-sdk
```

## Quick start

```python
from lws_testing import LwsSession

# Auto-discover resources from a CDK project
with LwsSession.from_cdk("../my-cdk-project") as session:
    dynamo = session.client("dynamodb")
    dynamo.put_item(TableName="Orders", Item={"id": {"S": "1"}})

# Auto-discover resources from a Terraform project
with LwsSession.from_hcl("../my-terraform-project") as session:
    s3 = session.client("s3")
    s3.put_object(Bucket="my-bucket", Key="test.txt", Body=b"hello")

# Explicit resource declaration
with LwsSession(
    tables=[{"name": "Orders", "partition_key": "id"}],
    queues=["OrderQueue"],
    buckets=["ReceiptsBucket"],
) as session:
    table = session.dynamodb("Orders")
    table.put({"id": {"S": "1"}, "status": {"S": "pending"}})
    items = table.scan()
    assert len(items) == 1
```

## pytest integration

The package registers pytest fixtures automatically via the `pytest11` entry point. Add a session fixture to your `conftest.py`:

```python
# conftest.py
import pytest

@pytest.fixture(scope="session")
def lws_session_spec():
    return {
        "tables": [{"name": "Orders", "partition_key": "id"}],
        "queues": ["OrderQueue"],
    }
```

Then use the `lws_session` fixture in your tests:

```python
def test_create_order(lws_session):
    client = lws_session.client("dynamodb")
    client.put_item(TableName="Orders", Item={"id": {"S": "42"}})

    table = lws_session.dynamodb("Orders")
    table.assert_item_exists({"id": {"S": "42"}})
```

## License

MIT
pindakaas 0.4.1
Boolean satisfiability (SAT) library with efficient encoding of complex constraints and solver interaction
Requires Python: >=3.8
Keywords: satisfiability, encoding, boolean, logic, sat

<p align="center">
  <img
    src="./assets/logo.svg"
    alt="pindakaas logo"
    height="300">

  <p align="center">
    A library to transform pseudo-Boolean and integer constraints into conjunctive normal form.
    <br />
    <br />
    <a href="https://crates.io/crates/pindakaas"><img src="https://img.shields.io/crates/v/pindakaas.svg"></a>
    <a href="https://crates.io/crates/pindakaas"><img src="https://docs.rs/pindakaas/badge.svg"></a>
  </p>
</p>


## Supported Constraints

- At most one (AMO)
  - Bitwise encoding
  - Ladder encoding
  - Pairwise encoding
- Cardinality constraints
  - Sorting Network encoding
- Boolean linear
  - Adder encoding
  - BDD encoding
  - Sequential Weight Counter encoding
  - Totalizer encoding
- Integer (linear)
  - Direct / Domain / Unary encoding
  - Order encoding
  - Binary encoding

## Installation and usage

Although the main Pindakaas library is written in rust, it is also available from Python.

### Rust

```bash
cargo add pindakaas
```

For more information about the Rust library, please visit the [official documentation](https://docs.rs/pindakaas).

### Python

```bash
pip install pindakaas
```

For more information about the Python library, please visit the [official documentation](https://pindakaas.readthedocs.io/en/latest/).

## Citation

If you want to cite Pindakaas please use our general software citation, in addition to any citation to a specific version or paper:

```biblatex
@software{Pindakaas,
author = {Bierlee, Hendrik and Dekker, Jip J.},
license = {MPL-2.0},
title = {{Pindakaas}},
url = {https://doi.org/10.5281/zenodo.10851855},
doi = {10.5281/zenodo.10851855},
}
```

Note that you might have to use `misc` instead of `software`, if your system does not support `software` as a type.

## Acknowledgements

This research was partially funded by the Australian Government through the Australian Research Council Industrial Transformation Training Centre in Optimisation Technologies, Integrated Methodologies, and Applications ([OPTIMA](https://optima.org.au)), Project ID IC200100009

## License

This library is made available under the [MPL-2.0](https://choosealicense.com/licenses/mpl-2.0/) license.
rebake 0.0.1
A spiritual successor to cruft for managing cookiecutter projects
Requires Python: >=3.12

# rebake

A spiritual successor to [cruft](https://github.com/cruft/cruft) for managing [cookiecutter](https://github.com/cookiecutter/cookiecutter) projects.

rebake improves on cruft in two key areas:

1. **Better conflict UX** — uses `git apply -3` to produce inline conflict markers instead of `.rej` files
2. **New variable detection** — prompts for variables added to the template since the project was last updated

## Requirements

- Python 3.12+
- [uv](https://docs.astral.sh/uv/)
- Git

## Installation

```bash
uv tool install rebake
```

Or add it to a project:

```bash
uv add rebake
```

## Usage

### `rebake check`

Check whether the project is up-to-date with its template.

```bash
rebake check [PROJECT_DIR]
```

Exit codes:
- `0` — up-to-date
- `1` — outdated
- `2` — error (e.g. `.cruft.json` not found)

### `rebake update`

Apply the latest template changes to the project.

```bash
rebake update [PROJECT_DIR]
```

rebake will:
1. Abort if there are uncommitted changes (commit or stash first)
2. Detect new variables added to the template and prompt for their values
3. Generate a diff between the old and new rendered templates
4. Apply the diff with `git apply -3` — conflicts appear as inline markers
5. Update `.cruft.json` with the new commit hash and any newly added variables

## Migrating from cruft

rebake reads `.cruft.json` as-is. No migration needed — just replace `cruft` with `rebake` in your commands.

```bash
# before
cruft check
cruft update

# after
rebake check
rebake update
```

## `.cruft.json` format

```json
{
  "template": "https://github.com/owner/template",
  "commit": "abc123...",
  "checkout": "main",
  "context": {
    "cookiecutter": {
      "project_name": "my-project",
      "author": "Jane Doe"
    }
  },
  "skip": ["go.sum", "*.lock"]
}
```

## Development

```bash
git clone https://github.com/kitagry/rebake
cd rebake
uv sync
uv run pytest
```