semvec/pypi-packages huggingface dataset:
django-remove-field 0.3.0
Handle deletion of django model field without downtime
Requires Python: >=3.11

[![Actions Status](https://github.com/procsea/django-remove-field/workflows/CI/badge.svg)](https://github.com/procsea/django-remove-field/actions)


# django_remove_field

Help to remove a django model fields without downtime.

## Soft deprecation

Use `@deprecated_fields(fieldnames=[])` to generate logs when one of the fieldnames is used:

```python
@deprecated_fields(["is_active"])
class ModelWithDeprecatedField(models.Model):
    name = models.CharField(max_length=64)
    is_active = models.BooleanField()
```

## Hard deprecation

Use `@removed_field(fieldnames=[])` to raise error when one of the fieldnames is used:

```python
@removed_fields(["is_active"])
class ModelWithRemovedField(models.Model):
    name = models.CharField(max_length=64)
    is_active = models.BooleanField(null=True)
```

## DB migration

When you run migration (`makemigrations`, `migrate`, ...), set the environment variable `DJANGO_REMOVE_FIELD_DISABLED`
to not generate remove field migration.

## developers

Run all tests with `make test`

We need to run twice tests with different value for environment variable to be able
to test the both case (using the decorator and ignoring decorator)
lego-store-availability 0.2.1
Check the availability of Lego™ product in stores
Requires Python: >=3.12

# LEGO™ store availability

Check the availability of Lego™ product in stores.

## Disclamer

This tools is not related in any way to LEGO™ and all of it's trademark.

This tools is not designed for malicious usage and any individual or group using it this way is responsible for is own actions.

## Install

```shell
pip3 install lego-store-availability
```

## Usage

First you need to create a `LegoAPI` object :

```python
from lego_store_availability import LegoAPI

lego = LegoAPI()
```

Then request a `Store` :

```python
from lego_store_availability import Store

store = lego.store(lang="fr-fr")
```

Finally retrieve a `Product` :

```python
from lego_store_availability import Product

product = store.product(
    product_id="10307",
)

print(product.name, product.availability)
```

## Contribute

- Clone or fork the repository.
- Install dev dependencies with `pip3 install -r dev-requirements.txt`
- Develop your feature or fix
- Lint with [pylint](https://pylint.pycqa.org/en/latest/)
- Test it with [pytest](https://pytest.org) under [tests/](./tests) directory
  - Mock HTTP requests with [responses](https://github.com/getsentry/responses)
- Push & create a Pull Request on `develop` branch
- Wait for the CI (Github Action) to exit in success state
sigstore-models 0.0.6
Pydantic based models for Sigstore's protobuf specifications
Requires Python: >=3.10

# sigstore-models

![PyPI - Version](https://img.shields.io/pypi/v/sigstore-models)

Pydantic-based data models for Sigstore.

These models mirror the subset of the [protobuf-specs] that
are used by the [sigstore-python] library.

## Goals

* Providing high-quality, type-safe data models to [sigstore-python].
* Matching Sigstore's (mostly protobuf influenced) JSON serialization
  format.

## Anti-goals

* Supporting protobuf serialization/deserialization.
* Doing anything besides mirroring a subset of the types in
  [protobuf-specs].

[protobuf-specs]: https://github.com/sigstore/protobuf-specs
[sigstore-python]: https://github.com/sigstore/sigstore-python