Release v2

[xSAVIKx]

This Pull Request marks the official release of v2.0.0 of the CloudEvents Python SDK. This version is a ground-up rewrite designed to provide a more robust, type-safe, and spec-compliant experience for Python developers.

🚀 Key Features and Improvements

• Protocol-Based Design: Replaced the base class with a Protocol-based architecture (BaseCloudEvent), allowing for more flexible and decoupled event implementations.
• Strict Validation: Events are now validated at construction time, ensuring compliance with the CloudEvents specification for attribute names, types, and values.
• Immutability and Explicit Getters: Events are immutable after creation. Dict-like access has been replaced with explicit getter methods (e.g., event.get_source(), event.get_type()) for better IDE support and type safety.
• Enhanced Protocol Bindings:
  • HTTP: New to_binary_event and from_http_event helpers using an HTTPMessage dataclass.
  • Kafka: Updated Kafka binding with better typing and frozen dataclasses for messages.
  • AMQP (New): Native support for AMQP 1.0 protocol binding.
• Custom Serialization: Introduced a Format protocol (replacing marshaller callbacks) to support custom serialization formats like YAML or Protobuf.
• Modern Python Support: Updated requirements to Python 3.10+ and removed heavy dependencies, making python-dateutil the only core requirement.
• Type Safety: Full mypy strict compliance across the core v2 codebase.

⚠️ Breaking Changes & Migration

The v2 release includes several breaking changes compared to v1. To ease the transition:

• Compatibility Layer: We have provided a cloudevents.v1 package. You can continue using v1-style logic by updating your imports (e.g., from cloudevents.v1.http import CloudEvent).
• Migration Guide: A comprehensive MIGRATION.md is included, detailing all architectural shifts, API changes, and import mappings.

✅ Verification Results

• Tests: All unit tests passed, including new conformance tests for the v2 core and compatibility tests for the v1 layer.
• Linting: 100% compliance with ruff and mypy (strict).
• Documentation: README and MIGRATION guides updated to reflect the new API.

[Klaudioz]

The root-level cloudevents/ directory (old v1 source) shadows src/cloudevents/ (v2). Running import cloudevents.core from a clean clone fails with ModuleNotFoundError. This needs to be resolved before merge either remove the root cloudevents/ directory (since v1 code now lives under src/cloudevents/v1/), or add a [tool.hatch.build.targets.wheel] config and ensure the test runner uses the installed package. As-is, the tests cannot run from source.

[xSAVIKx]

@Klaudioz there's no cloudevents root folder anymore, not sure what you are referring to.

Here's a complete work tree of the v2 branch:

├───.github
│   └───workflows
├───samples
│   ├───http-image-cloudevents
│   └───http-json-cloudevents
├───src
│   └───cloudevents
│       ├───core
│       │   ├───bindings
│       │   ├───formats
│       │   ├───v03
│       │   └───v1
│       └───v1
│           ├───abstract
│           ├───http
│           ├───kafka
│           ├───pydantic
│           │   ├───v1
│           │   └───v2
│           └───sdk
│               ├───converters
│               └───event
└───tests
    ├───test_cloudevents
    ├───test_core
    │   ├───test_bindings
    │   ├───test_format
    │   ├───test_v03
    │   └───test_v1
    └───test_v1_compat

I just grabbed a fresh clone and re-setup the whole env with:

• uv sync
• uv run pytest

[xSAVIKx]

@Klaudioz PTAL again. Let me know if you still have issues

[Klaudioz]

Rechecking this, I don’t think the packaging concern is real, so I’m retracting that review comment. The branch uses a src layout, and CI installs the project before running the test suite.