pydantic-plus-plus 0.2.0__tar.gz

pydantic_plus_plus-0.2.0/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @andonimichael

pydantic_plus_plus-0.2.0/.github/FUNDING.yml

@@ -0,0 +1 @@
+github: [andonimichael]

pydantic_plus_plus-0.2.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug report
+about: Report a bug or unexpected behavior
+labels: bug
+---
+
+## Description
+
+A clear description of the bug.
+
+## Expected Behavior
+
+What you expected to happen.
+
+## Actual Behavior
+
+What actually happened.
+
+## Steps to reproduce
+
+1.
+
+## Environment
+
+- Python version:
+- pydantic version:
+- pydantic-plus-plus version:

pydantic_plus_plus-0.2.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,13 @@
+---
+name: Feature request
+about: Suggest a feature
+labels: enhancement
+---
+
+## Description
+
+<!-- What would you like to see? -->
+
+## Use case
+
+<!-- Why is this useful? -->

pydantic_plus_plus-0.2.0/.github/pull_request_template.md

@@ -0,0 +1,11 @@
+## Summary
+
+Brief description of what this PR does and why.
+
+## Changes
+
+- ...
+
+## Testing
+
+How did you verify this change works?

pydantic_plus_plus-0.2.0/.github/release.yml

@@ -0,0 +1,8 @@
+changelog:
+  categories:
+    - title: "Commits"
+      labels:
+        - "*"
+  exclude:
+    labels:
+      - skip-changelog

pydantic_plus_plus-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,57 @@
+name: Continuous Integration
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  workflow_call:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v7
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.10"
+
+      - name: Install dependencies
+        run: uv sync --group dev
+
+      - name: Ruff check
+        run: uv run ruff check
+
+      - name: Ruff format
+        run: uv run ruff format --check
+
+      - name: Mypy
+        run: uv run mypy --config-file pyproject.toml
+
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v7
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: uv sync --group dev
+
+      - name: Run tests
+        run: uv run pytest

pydantic_plus_plus-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,134 @@
+name: Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      scope:
+        description: "Version Scope"
+        required: true
+        type: choice
+        options:
+          - patch
+          - minor
+          - major
+        default: patch
+
+permissions:
+  contents: write
+  id-token: write
+
+jobs:
+  ci:
+    uses: ./.github/workflows/ci.yml
+
+  release:
+    name: Bump Version, Tag & Release
+    needs: ci
+    runs-on: ubuntu-latest
+    outputs:
+      new_version: ${{ steps.bump.outputs.new_version }}
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          token: ${{ secrets.PYDANTIC_PLUS_PLUS_RELEASE_PAT }}
+
+      - name: Configure git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+
+      - name: Bump version
+        id: bump
+        run: |
+          chmod +x scripts/release.sh
+          ./scripts/release.sh ${{ inputs.scope }}
+
+      - name: Commit and tag
+        run: |
+          TAG="v${{ steps.bump.outputs.new_version }}"
+          git add pyproject.toml
+          git commit -m "$(cat <<EOF
+          Release ${TAG}
+
+          Scope: ${{ inputs.scope }}
+          Previous: v${{ steps.bump.outputs.old_version }}
+          EOF
+          )"
+          git tag -a "$TAG" -m "Release ${TAG}"
+          git push origin main "$TAG"
+
+  build:
+    needs: release
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          ref: v${{ needs.release.outputs.new_version }}
+
+      - uses: astral-sh/setup-uv@v7
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.10"
+
+      - name: Build package
+        run: uv build
+
+      - name: Upload artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish-pypi:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - name: Download artifacts
+        uses: actions/download-artifact@v6
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+  github-release:
+    needs: [release, build]
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Download artifacts
+        uses: actions/download-artifact@v6
+        with:
+          name: dist
+          path: dist/
+
+      - name: Create GitHub Release
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          TAG="v${{ needs.release.outputs.new_version }}"
+          PREV_TAG=$(git tag --sort=-v:refname | grep -E '^v[0-9]' | sed -n '2p' || true)
+
+          ARGS=(--title "${TAG}" --generate-notes)
+
+          if [[ -n "$PREV_TAG" ]]; then
+            ARGS+=(--notes-start-tag "$PREV_TAG")
+          fi
+
+          VERSION="${{ needs.release.outputs.new_version }}"
+          MAJOR="${VERSION%%.*}"
+          if [[ "$MAJOR" == "0" ]]; then
+            ARGS+=(--prerelease)
+          fi
+
+          gh release create "${TAG}" dist/* "${ARGS[@]}"

pydantic_plus_plus-0.2.0/.gitignore

@@ -0,0 +1,20 @@
+# Python
+__pycache__/
+.venv/
+
+# OS files
+.DS_Store
+Thumbs.db
+
+# Editor files
+*.swp
+*.swo
+*~
+.idea/
+.vscode/
+.claude/
+
+# Dependencies
+.venv/
+.pytest_cache/
+.ruff_cache/

pydantic_plus_plus-0.2.0/.pre-commit-config.yaml

@@ -0,0 +1,29 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: check-executables-have-shebangs
+      - id: check-json
+      - id: check-toml
+      - id: check-yaml
+      - id: detect-private-key
+      - id: end-of-file-fixer
+      - id: pretty-format-json
+        args: ["--indent", "4", "--autofix"]
+      - id: trailing-whitespace
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.15.8
+    hooks:
+      - id: ruff-check
+        args: [--fix]
+      - id: ruff-format
+
+  - repo: local
+    hooks:
+      - id: mypy
+        name: mypy
+        entry: .venv/bin/mypy --config-file pyproject.toml
+        language: system
+        types: [python]
+        verbose: true

pydantic_plus_plus-0.2.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,89 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, please email andoni.m.garcia@gmail.com.
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

pydantic_plus_plus-0.2.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Andoni Michael Garcia
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

pydantic_plus_plus-0.2.0/PKG-INFO

@@ -0,0 +1,229 @@
+Metadata-Version: 2.4
+Name: pydantic-plus-plus
+Version: 0.2.0
+Summary: Pydantic++ | Utilities to improve on the core Pydantic library
+Project-URL: Homepage, https://github.com/andonimichael/pydantic-plus-plus
+Project-URL: Repository, https://github.com/andonimichael/pydantic-plus-plus
+Author-email: Andoni Garcia <andoni.m.garcia@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: pydantic>=2.0
+Description-Content-Type: text/markdown
+
+# Pydantic++
+
+Pydantic++ is a suite of utilities to improve upon the core [Pydantic](https://github.com/pydantic/pydantic) library. We stand on the shoulders of giants here. Huge kudos to the Pydantic team for all their hard work building an amazing product.
+
+## Installation
+
+```bash
+pip install pydantic-plus-plus
+```
+
+Requires Python 3.10+ and Pydantic 2.0+.
+
+If you use [mypy](https://github.com/python/mypy) for type checking, please also add our plugin to your `mypy` configuration.
+
+```toml
+[tool.mypy]
+plugins = ["pydantic.mypy", "pydantic_plus_plus.mypy"]
+```
+
+## Partial Models
+
+`partial` creates a `PartialBaseModel`, a variant of the given Pydantic `BaseModel` where every field is `Optional` with a default of `None`. This is the type-safe way to represent partial updates (PATCH payloads, upsert data, sparse sync records) without manually duplicating each model with every field made optional.
+
+### Usage
+
+```python
+from pydantic import BaseModel
+from pydantic_plus_plus import partial
+
+class User(BaseModel):
+    name: str
+    age: int
+    email: str
+
+PartialUser = partial(User)
+```
+
+The resulting `PartialUser` class accepts any subset of fields:
+
+```python
+patch = PartialUser(name="Alice")
+patch.name   # "Alice"
+patch.age    # None
+patch.email  # None
+```
+
+Use `model_dump(exclude_unset=True)` to get only the fields that were explicitly provided — the standard pattern for database partial updates:
+
+```python
+patch = PartialUser(name="Alice", age=31)
+patch.model_dump(exclude_unset=True)
+# {"name": "Alice", "age": 31}
+```
+
+### Recursive Partials
+
+By default, nested `BaseModel` fields are also partialized. This means you can provide incomplete nested data:
+
+```python
+class Address(BaseModel):
+    street: str
+    city: str
+    state: str
+    zip_code: str
+
+class User(BaseModel):
+    name: str
+    address: Address
+
+PartialUser = partial(User)
+
+# Only update the city — street, state, zip_code are not required
+patch = PartialUser(address={"city": "New York City"})
+```
+
+Disable this with `recursive=False` to require complete nested models when provided:
+
+```python
+PartialUser = partial(User, recursive=False)
+
+# This now requires all Address fields
+patch = PartialUser(address=Address(
+    street="123 1st Ave",
+    city="New York",
+    state="NY",
+    zip_code="10001",
+))
+```
+
+Recursive partialization handles `list[Model]`, `dict[str, Model]`, `Optional[Model]`, and self-referencing models.
+
+### Applying Partials
+
+Use `.apply()` to deep-merge a partial into an existing model instance. Only explicitly-set fields are merged; everything else is preserved:
+
+```python
+user = User(
+    name="Alice",
+    age=30,
+    email="alice@example.com",
+    address=Address(street="123 1st Ave", city="New York", state="NY", zip_code="10001"),
+)
+
+patch = PartialUser(age=31, address={"city": "New York City"})
+updated = patch.apply(user)
+
+updated.name             # "Alice" — preserved
+updated.age              # 31 — updated
+updated.address.street   # "123 1st Ave" — preserved
+updated.address.city     # "New York City" — updated
+```
+
+`.apply()` returns a new instance of the original model type. The original is never mutated.
+
+### What Partials Preserve
+
+- **Field metadata** — descriptions, constraints (`min_length`, `ge`, etc.), and aliases are carried over. Constraints are enforced when a non-`None` value is provided.
+- **Serialization** — custom type serializers defined via `Annotated` (e.g., UUID-to-string) work as expected.
+- **JSON Schema** — `model_json_schema()` produces a valid schema with all properties defaulting to `null`.
+- **Validation** — `model_validate()`, `model_validate_json()`, and `model_dump_json()` all work.
+
+### What Partials Don't Inherit
+
+Partial models are standalone classes that subclass `PartialBaseModel`, not the original model. This means:
+
+- `@field_validator` and `@model_validator` decorators on the original are **not** inherited. This is intentional — validators that enforce required-field invariants would reject the partial data.
+- `isinstance(patch, User)` is `False`. Use `isinstance(patch, PartialBaseModel)` instead.
+
+### Alternative Syntax
+
+You can also use the class method:
+
+```python
+PartialUser = PartialBaseModel.from_model(User)
+```
+
+Both syntaxes return the same cached class.
+
+### Caching
+
+Partial classes are cached by (model, recursive) pair. Calling `partial(User)` multiple times returns the same class:
+
+```python
+partial(User) is partial(User)           # True
+partial(User, recursive=False) is partial(User, recursive=True)  # False
+```
+
+## Mypy Plugin
+
+Pydantic++ ships a mypy plugin that gives partial models full type safety. Without it, mypy sees `partial(User)` as returning a generic type and can't validate field access or constructor arguments.
+
+With the plugin enabled, mypy understands that `PartialUser` has `name: str | None`, `age: int | None`, etc., and will type-check constructor calls and attribute access accordingly.
+
+### Setup
+
+Add the plugin to your mypy configuration:
+
+```toml
+# pyproject.toml
+[tool.mypy]
+plugins = ["pydantic.mypy", "pydantic_plus_plus.mypy"]
+```
+
+The plugin works alongside the standard Pydantic mypy plugin. Order does not matter.
+
+### What the Plugin Enables
+
+Without the plugin:
+
+```python
+PartialUser = partial(User)
+
+def update(p: PartialUser) -> None:  # mypy error: not valid as a type
+    p.model_dump()                   # mypy error: has no attribute "model_dump"
+```
+
+With the plugin, both lines type-check cleanly — no `# type: ignore` needed.
+
+## Comparable Packages
+
+### Why Pydantic++ over pydantic-partial?
+
+Pydantic++ offers a similar feature set, but takes a different philosophical approach than [pydantic-partial](https://github.com/team23/pydantic-partial) that is more aligned with SOLID Object Oriented design principles.
+
+Here's how the two differ:
+
+| | Pydantic++ | pydantic-partial |
+|---|---|---|
+| Partial models | All fields optional | All fields optional |
+| Selective fields | Planned | `model_as_partial("name", "email")` |
+| Dot-notation nesting | Planned | `model_as_partial("address.city")` |
+| Wildcard nesting | Planned | `model_as_partial("address.*")` |
+| Field metadata preservation | Yes | Yes |
+| Caching | Yes | Yes |
+| Recursive by default | Yes | No (opt-in) |
+| Mypy plugin | Yes | No |
+| `.apply()` deep merge | Yes | No |
+| Standalone partial classes | Yes — partials don't subclass the original | No — partials subclass the original |
+
+#### Philosophical Differences
+
+`pydantic-partial`'s partials subclass the original model, so `isinstance(patch, User)` is `True`. This violates the Liskov Substitution Principle — a partial `User` weakens the preconditions of the original (required fields become optional), meaning code that expects a complete `User` can silently receive one with `None` fields. In addition to breaking LSP, this also causes problems for type checkers because the subclass relationship tells type checkers the partial *is* a `User`.
+
+Pydantic++ takes a different philosophical approach, where partials are standalone classes. This preserves LSP. Additionally, because `isinstance(patch, User)` is `False`, the type checker can enforce the boundary between partial and complete data. Users must go through `.apply()` to produce a real `User`, making the conversion explicit and safe.
+
+#### Mypy plugin
+
+This is a well known limitation of `pydantic-partial`, which their README calls out as "a massive amount of work while being kind of a bad hack." Pydantic++ ships a mypy plugin that synthesizes full `TypeInfo` objects, giving users field-level type checking, constructor validation, and IDE autocompletion with zero `# type: ignore` comments.
+
+#### `.apply()` deep merge
+
+pydantic-partial creates partial models but has no built-in way to merge a partial back into an existing instance. Pydantic++ provides `.apply()` which recursively merges only explicitly-set fields, preserving untouched nested data.
+
+## License
+
+MIT