DataExcept 0.1.0__tar.gz → 0.2.1__tar.gz

dataexcept-0.2.1/CHANGELOG.md

@@ -0,0 +1,132 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.2.1] - 2026-08-24
+
+Documentation and CLI fixes. 0.2.0's README is what PyPI renders as the
+project description, and its quick-start example did not run.
+
+### Fixed
+
+- `python -m dataexcept --version` reported `__main__.py` as the program name
+  instead of `dataexcept`, because argparse defaults `prog` to `sys.argv[0]`.
+- `dataexcept list` imported the deprecated `job_exceptions` shim to build its
+  output, so it emitted a `DeprecationWarning` at anyone who merely wanted to
+  see what the package offers, and it advertised `ConnectionError` and
+  `TimeoutError` alongside their replacements. Deprecated modules are now
+  skipped; the listing is 98 names, matching the classes the package defines.
+- README's quick-start example began `from dataexcept import ValidationError,
+  ModelTrainingError`, which raises `ImportError` — `ModelTrainingError` is in
+  `dataexcept.datascience_exceptions` and is not re-exported at the top level.
+- `docs/advanced_usage.md` taught `from dataexcept.job_exceptions import
+  JobError`, the deprecated path.
+- README's comparison table showed exception messages without the
+  `[ClassName]` prefix the classes actually emit, its sample `dataexcept list`
+  output did not match the real alphabetical listing, its exception count and
+  CLI version were stale, and its end-to-end example used `np.log` without
+  importing numpy.
+
+### Added
+
+- Tests that read the documentation: every `from dataexcept... import ...` in
+  README and `docs/` must resolve, no example may import a deprecated module,
+  and the README's exception count must match the package. Checked that these
+  fail when the original defects are reintroduced.
+
+## [0.2.0] - 2026-08-24
+
+### Changed
+
+- **`ConnectionError` is now `ServiceConnectionError`, and `TimeoutError` is
+  now `OperationTimeoutError`.** The old names shadowed Python builtins without
+  inheriting from them, so after `from dataexcept import ConnectionError` an
+  `except ConnectionError:` in that module silently stopped catching real
+  socket failures.
+- **`datascience_exceptions.SerializationError` is now
+  `ModelSerializationError`**, and **`pipeline_exceptions.FeatureEngineeringError`
+  is now `FeaturePreprocessingError`.** Each of those names previously referred
+  to two different classes in different modules, so catching one silently
+  missed the other.
+- Project metadata moved from Poetry's `[tool.poetry]` table to the standard
+  PEP 621 `[project]` table, clearing every `poetry check` deprecation. The
+  license is now an SPDX expression (PEP 639), so the built metadata carries
+  `License-Expression: MIT` and the redundant license classifier is gone.
+  Wheel and sdist contents are otherwise unchanged.
+- `dataexcept.job_exceptions` now names its removal version, 1.0.0, in both the
+  warning and the module docstring.
+
+### Deprecated
+
+- `ConnectionError`, `TimeoutError`, `datascience_exceptions.SerializationError`
+  and `pipeline_exceptions.FeatureEngineeringError`. All four still resolve, to
+  the **same class object** as their replacement, so existing `except` clauses
+  keep working; touching one emits a `DeprecationWarning` naming the
+  replacement and 1.0.0 as the removal. Importing the package does not warn.
+  Find remaining uses with `python -W error::DeprecationWarning -m pytest`.
+
+### Added
+
+- A published [API stability policy](https://diogoribeiro7.github.io/DataExcept/stability/)
+  stating what is public, what each kind of change costs in version terms, the
+  deprecation process, and how to migrate off the 0.2.0 renames.
+- Security scanning: CodeQL, and pip-audit against the runtime and
+  documentation dependency sets, on push, pull request and weekly — advisories
+  are published against code that has not changed. Pull requests also get a
+  dependency review failing at moderate severity.
+- Complexity and security linting via ruff's mccabe (`C90`) and flake8-bandit
+  (`S`) rule sets, so neither needs a separate tool. Complexity is capped at 8;
+  the highest score in the package is 6.
+- A regression guard that fails if any exported name ever shadows a builtin
+  again.
+- `__all__` on `dataexcept.logging_helpers`, the one public module without one.
+
+### Fixed
+
+- `dataexcept.__version__` and `tests/test_version.py` read the version out of
+  `pyproject.toml` when the package is not installed, and were still looking in
+  `[tool.poetry]`. They now read `[project]`.
+- `examples/example_usage.py` raised `TimeoutError` with keyword arguments the
+  builtin does not accept — a live instance of the shadowing hazard.
+
+
+## [0.1.0] - 2026-08-24
+
+First public release.
+
+### Added
+
+- Hierarchical exception classes for data science, machine learning and data
+  engineering workflows. Catch a specific failure or a broad category, and get
+  a message that names the value that caused it rather than a bare
+  `ValueError`.
+- Domain modules for validation, configuration, authentication, parsing,
+  serialization, scheduling, notification, lifecycle and external-service
+  errors, plus dedicated pandas, database, network, I/O, pipeline and security
+  exception groups.
+- `dataexcept.logging_helpers` with `log_exception`, `log_and_raise` and
+  `log_then_raise`, for logging exceptions with structured context and
+  re-raising without losing the traceback.
+- A `dataexcept` command-line entry point that lists the exported exception
+  classes and reports the installed version.
+- A `py.typed` marker, backed by a mypy-clean codebase that CI enforces, so
+  downstream type checkers get annotations that are actually correct.
+- Documentation at
+  [diogoribeiro7.github.io/DataExcept](https://diogoribeiro7.github.io/DataExcept/),
+  including an API reference generated from the docstrings.
+
+### Notes
+
+- Supports Python 3.10 through 3.13.
+- Published to PyPI via OIDC trusted publishing; no long-lived API token is
+  involved in a release.
+
+[Unreleased]: https://github.com/DiogoRibeiro7/DataExcept/compare/v0.2.1...HEAD
+[0.2.1]: https://github.com/DiogoRibeiro7/DataExcept/compare/v0.2.0...v0.2.1
+[0.2.0]: https://github.com/DiogoRibeiro7/DataExcept/compare/v0.1.0...v0.2.0
+[0.1.0]: https://github.com/DiogoRibeiro7/DataExcept/releases/tag/v0.1.0

{dataexcept-0.1.0 → dataexcept-0.2.1}/CITATION.cff

@@ -1,7 +1,7 @@
 cff-version: 1.2.0
 message: "If you use this software, please cite it using the following metadata."
 title: "DataExcept"
-version: "0.1.0"
+version: "0.2.1"
 authors:
   - family-names: "Ribeiro"
     given-names: "Diogo"
@@ -11,4 +11,4 @@ authors:
 type: software
 url: "https://github.com/DiogoRibeiro7/DataExcept"
 repository-code: "https://github.com/DiogoRibeiro7/DataExcept"
-date-released: "2025-06-16"
+date-released: "2026-08-24"

{dataexcept-0.1.0 → dataexcept-0.2.1}/PKG-INFO

@@ -1,8 +1,8 @@
 Metadata-Version: 2.4
 Name: DataExcept
-Version: 0.1.0
+Version: 0.2.1
 Summary: A Python package providing structured, easily-extendable custom exception types.
-License: MIT
+License-Expression: MIT
 License-File: LICENSE
 Keywords: exceptions,errors,logging
 Author: Diogo Ribeiro
@@ -10,13 +10,12 @@ Author-email: dfr@esmad.ipp.pt
 Maintainer: Diogo Ribeiro
 Maintainer-email: diogo.debastos.ribeiro@gmail.com
 Requires-Python: >=3.10,<3.14
-Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
-Classifier: Programming Language :: Python :: 3 :: Only
 Requires-Dist: tomli ; python_version < "3.11"
 Project-URL: Changelog, https://github.com/DiogoRibeiro7/DataExcept/releases
 Project-URL: Documentation, https://diogoribeiro7.github.io/DataExcept/
@@ -35,15 +34,15 @@ Description-Content-Type: text/markdown
 
 ❌ Without DataExcept            | ✅ With DataExcept
 ------------------------------- | -------------------------------------------------------------------------------------
-`ValueError: Invalid value`     | `DataValidationError: Invalid value for 'age': -1`
-`RuntimeError: Training failed` | `ConvergenceError: Model 'RandomForest' failed to converge after 100 iterations`
-`Exception: Prediction error`   | `ModelInferenceError: Inference failed for model 'CNN': CUDA out of memory`
-`KeyError: column not found`    | `MissingColumnError: Missing required column 'customer_id' in DataFrame 'sales_data'`
+`ValueError: Invalid value`     | `DataValidationError: [DataValidationError:age] Invalid value for 'age': -1`
+`RuntimeError: Training failed` | `ConvergenceError: [ConvergenceError] Model 'RandomForest' failed to converge after 100 iterations`
+`Exception: Prediction error`   | `ModelInferenceError: [ModelInferenceError:CNN] Inference failed for model 'CNN': CUDA out of memory`
+`KeyError: column not found`    | `MissingColumnError: [MissingColumnError] Missing required column 'customer_id' in DataFrame 'sales_data'`
 
 ## 🎯 Key Features
 
 - **🏗️ Hierarchical Structure**: Catch specific errors or broad categories
-- **📊 Data Science Focused**: 40+ exceptions covering ML pipelines, feature engineering, model training
+- **📊 Data Science Focused**: 98 exception classes covering ML pipelines, feature engineering, model training
 - **🔧 Production Ready**: Comprehensive logging helpers and error context
 - **📚 Academic Quality**: Proper documentation, type hints, and citation support
 - **🐍 Python 3.10+**: Modern Python with full type safety
@@ -68,8 +67,8 @@ poetry install
 ### Basic Usage
 
 ```python
-from dataexcept import ValidationError, ModelTrainingError
-from dataexcept.datascience_exceptions import DataLoadingError
+from dataexcept import ValidationError
+from dataexcept.datascience_exceptions import DataLoadingError, ModelTrainingError
 import pandas as pd
 
 # Data validation with context
@@ -215,17 +214,18 @@ except Exception as exc:
 ### Command Line Interface
 
 ```bash
-# List all available exception classes
+# List every exception class the package exports (98 of them, alphabetically)
 $ dataexcept list
-JobError
-ValidationError
-DataScienceError
-ModelTrainingError
-... (40+ more)
+ApiError
+AuthenticationError
+AuthorizationError
+BatchProcessingError
+BiasDetectionError
+...
 
 # Check version
 $ dataexcept --version
-dataexcept 0.1.0
+dataexcept 0.2.1
 ```
 
 ## 🎯 Use Cases
@@ -256,6 +256,7 @@ dataexcept 0.1.0
 """
 Complete ML pipeline with DataExcept error handling
 """
+import numpy as np
 import pandas as pd
 from sklearn.ensemble import RandomForestClassifier
 from dataexcept import ValidationError
@@ -360,6 +361,7 @@ through [SECURITY.md](SECURITY.md), not the public issue tracker.
 
 - **Full Documentation**: [diogoribeiro7.github.io/DataExcept](https://diogoribeiro7.github.io/DataExcept/)
 - **API Reference**: [API Docs](https://diogoribeiro7.github.io/DataExcept/api/)
+- **API Stability**: [What is public and what may change](https://diogoribeiro7.github.io/DataExcept/stability/)
 - **Advanced Usage**: [Advanced Guide](https://diogoribeiro7.github.io/DataExcept/advanced_usage/)
 - **CLI Reference**: [CLI Guide](https://diogoribeiro7.github.io/DataExcept/cli/)
 - **Changelog**: [CHANGELOG.md](CHANGELOG.md)
@@ -369,12 +371,12 @@ through [SECURITY.md](SECURITY.md), not the public issue tracker.
 If you use DataExcept in your research, please cite it:
 
 ```bibtex
-@software{ribeiro_dataexcept_2025,
+@software{ribeiro_dataexcept_2026,
   author = {Ribeiro, Diogo},
   title = {DataExcept: Structured Exception Handling for Data Science},
   url = {https://github.com/DiogoRibeiro7/DataExcept},
-  version = {0.1.0},
-  year = {2025},
+  version = {0.2.1},
+  year = {2026},
   publisher = {GitHub}
 }
 ```

{dataexcept-0.1.0 → dataexcept-0.2.1}/README.md

@@ -8,15 +8,15 @@
 
 ❌ Without DataExcept            | ✅ With DataExcept
 ------------------------------- | -------------------------------------------------------------------------------------
-`ValueError: Invalid value`     | `DataValidationError: Invalid value for 'age': -1`
-`RuntimeError: Training failed` | `ConvergenceError: Model 'RandomForest' failed to converge after 100 iterations`
-`Exception: Prediction error`   | `ModelInferenceError: Inference failed for model 'CNN': CUDA out of memory`
-`KeyError: column not found`    | `MissingColumnError: Missing required column 'customer_id' in DataFrame 'sales_data'`
+`ValueError: Invalid value`     | `DataValidationError: [DataValidationError:age] Invalid value for 'age': -1`
+`RuntimeError: Training failed` | `ConvergenceError: [ConvergenceError] Model 'RandomForest' failed to converge after 100 iterations`
+`Exception: Prediction error`   | `ModelInferenceError: [ModelInferenceError:CNN] Inference failed for model 'CNN': CUDA out of memory`
+`KeyError: column not found`    | `MissingColumnError: [MissingColumnError] Missing required column 'customer_id' in DataFrame 'sales_data'`
 
 ## 🎯 Key Features
 
 - **🏗️ Hierarchical Structure**: Catch specific errors or broad categories
-- **📊 Data Science Focused**: 40+ exceptions covering ML pipelines, feature engineering, model training
+- **📊 Data Science Focused**: 98 exception classes covering ML pipelines, feature engineering, model training
 - **🔧 Production Ready**: Comprehensive logging helpers and error context
 - **📚 Academic Quality**: Proper documentation, type hints, and citation support
 - **🐍 Python 3.10+**: Modern Python with full type safety
@@ -41,8 +41,8 @@ poetry install
 ### Basic Usage
 
 ```python
-from dataexcept import ValidationError, ModelTrainingError
-from dataexcept.datascience_exceptions import DataLoadingError
+from dataexcept import ValidationError
+from dataexcept.datascience_exceptions import DataLoadingError, ModelTrainingError
 import pandas as pd
 
 # Data validation with context
@@ -188,17 +188,18 @@ except Exception as exc:
 ### Command Line Interface
 
 ```bash
-# List all available exception classes
+# List every exception class the package exports (98 of them, alphabetically)
 $ dataexcept list
-JobError
-ValidationError
-DataScienceError
-ModelTrainingError
-... (40+ more)
+ApiError
+AuthenticationError
+AuthorizationError
+BatchProcessingError
+BiasDetectionError
+...
 
 # Check version
 $ dataexcept --version
-dataexcept 0.1.0
+dataexcept 0.2.1
 ```
 
 ## 🎯 Use Cases
@@ -229,6 +230,7 @@ dataexcept 0.1.0
 """
 Complete ML pipeline with DataExcept error handling
 """
+import numpy as np
 import pandas as pd
 from sklearn.ensemble import RandomForestClassifier
 from dataexcept import ValidationError
@@ -333,6 +335,7 @@ through [SECURITY.md](SECURITY.md), not the public issue tracker.
 
 - **Full Documentation**: [diogoribeiro7.github.io/DataExcept](https://diogoribeiro7.github.io/DataExcept/)
 - **API Reference**: [API Docs](https://diogoribeiro7.github.io/DataExcept/api/)
+- **API Stability**: [What is public and what may change](https://diogoribeiro7.github.io/DataExcept/stability/)
 - **Advanced Usage**: [Advanced Guide](https://diogoribeiro7.github.io/DataExcept/advanced_usage/)
 - **CLI Reference**: [CLI Guide](https://diogoribeiro7.github.io/DataExcept/cli/)
 - **Changelog**: [CHANGELOG.md](CHANGELOG.md)
@@ -342,12 +345,12 @@ through [SECURITY.md](SECURITY.md), not the public issue tracker.
 If you use DataExcept in your research, please cite it:
 
 ```bibtex
-@software{ribeiro_dataexcept_2025,
+@software{ribeiro_dataexcept_2026,
   author = {Ribeiro, Diogo},
   title = {DataExcept: Structured Exception Handling for Data Science},
   url = {https://github.com/DiogoRibeiro7/DataExcept},
-  version = {0.1.0},
-  year = {2025},
+  version = {0.2.1},
+  year = {2026},
   publisher = {GitHub}
 }
 ```

{dataexcept-0.1.0 → dataexcept-0.2.1}/dataexcept/__init__.py

@@ -28,11 +28,11 @@ from . import (
     pipeline_exceptions,
     security_exceptions,
 )
+from ._deprecation import resolve_deprecated
 from .exceptions import (  # noqa: F401
     AuthenticationError,
     AuthorizationError,
     ConfigurationError,
-    ConnectionError,
     CronExpressionError,
     DependencyError,
     DeserializationError,
@@ -40,22 +40,27 @@ from .exceptions import (  # noqa: F401
     JobCancellationError,
     JobError,
     NotificationError,
+    OperationTimeoutError,
     ParsingError,
     ResourceNotFoundError,
     ScheduleConflictError,
     SerializationError,
-    TimeoutError,
+    ServiceConnectionError,
     ValidationError,
     WebhookError,
 )
-from .logging_helpers import log_and_raise, log_exception, log_then_raise
+from .logging_helpers import (
+    log_and_raise,
+    log_exception,
+    log_then_raise,
+)
 
 try:
     __version__ = metadata.version("DataExcept")
 except metadata.PackageNotFoundError:  # pragma: no cover - fallback during dev
     _root = Path(__file__).resolve().parents[1]
     with open(_root / "pyproject.toml", "rb") as _f:
-        __version__ = tomllib.load(_f)["tool"]["poetry"]["version"]
+        __version__ = tomllib.load(_f)["project"]["version"]
 
 __all__ = list(_exceptions.__all__) + [
     "datascience_exceptions",
@@ -73,9 +78,17 @@ __all__ = list(_exceptions.__all__) + [
 ]
 
 
+#: Renamed in 0.2.0 because they shadowed Python builtins without inheriting
+#: from them. Each alias is the same class object as its replacement.
+_DEPRECATED_ALIASES = {
+    "ConnectionError": ServiceConnectionError,
+    "TimeoutError": OperationTimeoutError,
+}
+
+
 def __getattr__(name: str) -> Any:
     if name == "job_exceptions":
         module = import_module("dataexcept.job_exceptions")
         globals()[name] = module
         return module
-    raise AttributeError(f"module {__name__!r} has no attribute {name!r}")
+    return resolve_deprecated(__name__, _DEPRECATED_ALIASES, name)

{dataexcept-0.1.0 → dataexcept-0.2.1}/dataexcept/__main__.py

@@ -12,9 +12,14 @@ from typing import Iterable
 from . import __path__ as _PKG_PATH
 from . import __version__
 
+#: Deprecated compatibility shims. Listing these would advertise names that are
+#: scheduled for removal, and importing them emits a DeprecationWarning at
+#: anyone who merely wanted to see what the package offers.
+_DEPRECATED_MODULES = frozenset({"dataexcept.job_exceptions"})
+
 
 def _iter_exception_modules() -> Iterable[ModuleType]:
-    """Yield every submodule that explicitly defines ``__all__``."""
+    """Yield every non-deprecated submodule that explicitly defines ``__all__``."""
     allowed_suffixes = ("exceptions", "_exceptions")
 
     for module_info in pkgutil.walk_packages(
@@ -22,6 +27,8 @@ def _iter_exception_modules() -> Iterable[ModuleType]:
     ):
         if not module_info.name.endswith(allowed_suffixes):
             continue
+        if module_info.name in _DEPRECATED_MODULES:
+            continue
         try:
             module = import_module(module_info.name)
         except ImportError as exc:  # pragma: no cover - defensive guard
@@ -53,7 +60,11 @@ def _list_exceptions() -> None:
 
 def main(argv: list[str] | None = None) -> None:
     """Entry point for the ``dataexcept`` command."""
-    parser = argparse.ArgumentParser(description="Utilities for DataExcept")
+    parser = argparse.ArgumentParser(
+        # Without this, `python -m dataexcept --version` reports "__main__.py".
+        prog="dataexcept",
+        description="Utilities for DataExcept",
+    )
     parser.add_argument(
         "--version",
         action="version",

dataexcept-0.2.1/dataexcept/_deprecation.py

@@ -0,0 +1,38 @@
+"""Internal support for names that have been renamed.
+
+A rename keeps the old name working as an alias bound to the *same* class
+object, so an existing ``except OldName:`` keeps catching exactly what it
+caught before -- the alias is not a separate class.
+
+Access goes through a PEP 562 module ``__getattr__`` rather than a plain
+``OldName = NewName`` assignment, because an assignment cannot warn. This is
+private; see the stability policy for the user-facing contract.
+"""
+
+from __future__ import annotations
+
+import warnings
+from typing import Any, Mapping
+
+#: Version in which every currently deprecated alias is removed.
+REMOVED_IN = "1.0.0"
+
+
+def resolve_deprecated(module: str, aliases: Mapping[str, Any], name: str) -> Any:
+    """Return the target of the deprecated *name*, warning first.
+
+    Raises ``AttributeError`` for anything not in *aliases*, so normal
+    attribute lookup on the module keeps behaving normally.
+    """
+    try:
+        target = aliases[name]
+    except KeyError:
+        raise AttributeError(f"module {module!r} has no attribute {name!r}") from None
+    warnings.warn(
+        f"{module}.{name} is deprecated and will be removed in {REMOVED_IN}; "
+        f"use {target.__name__} instead",
+        DeprecationWarning,
+        # resolve_deprecated -> __getattr__ -> the caller we want to blame.
+        stacklevel=3,
+    )
+    return target

{dataexcept-0.1.0 → dataexcept-0.2.1}/dataexcept/datascience_exceptions/__init__.py

@@ -1,5 +1,8 @@
 """Custom exceptions for data science workflows."""
 
+from typing import Any
+
+from .._deprecation import resolve_deprecated
 from .base import DataScienceError
 from .ingestion import (
     DataAugmentationError,
@@ -18,8 +21,8 @@ from .operations import (
     DataDriftError,
     DataExportError,
     DeploymentError,
+    ModelSerializationError,
     ResourceLimitError,
-    SerializationError,
 )
 from .training import (
     BiasDetectionError,
@@ -59,7 +62,7 @@ __all__ = [
     "HyperparameterError",
     "ModelEvaluationError",
     "PredictionError",
-    "SerializationError",
+    "ModelSerializationError",
     "DeploymentError",
     "DataDriftError",
     "ResourceLimitError",
@@ -83,3 +86,11 @@ __all__ = [
     "FeatureScalingError",
     "ModelCompatibilityError",
 ]
+
+#: Renamed in 0.2.0: this named the same thing as
+#: ``dataexcept.exceptions.SerializationError`` while being a different class.
+_DEPRECATED_ALIASES = {"SerializationError": ModelSerializationError}
+
+
+def __getattr__(name: str) -> Any:
+    return resolve_deprecated(__name__, _DEPRECATED_ALIASES, name)

{dataexcept-0.1.0 → dataexcept-0.2.1}/dataexcept/datascience_exceptions/operations.py

@@ -7,7 +7,7 @@ from typing import Any, Optional
 from .base import DataScienceError
 
 
-class SerializationError(DataScienceError):
+class ModelSerializationError(DataScienceError):
     """
     Raised when saving or loading a model fails.
 
@@ -30,7 +30,7 @@ class SerializationError(DataScienceError):
         super().__init__(message)
 
     def __str__(self) -> str:
-        return f"[SerializationError] {self.path}"
+        return f"[ModelSerializationError] {self.path}"
 
 
 class DeploymentError(DataScienceError):

{dataexcept-0.1.0 → dataexcept-0.2.1}/dataexcept/exceptions/__init__.py

@@ -1,12 +1,15 @@
 # __init__.py
+from typing import Any
+
+from .._deprecation import resolve_deprecated
 from .authentication import AuthenticationError, AuthorizationError
 from .base import JobError
 from .configuration import ConfigurationError
 from .external import (
-    ConnectionError,
     DependencyError,
+    OperationTimeoutError,
     ResourceNotFoundError,
-    TimeoutError,
+    ServiceConnectionError,
 )
 from .lifecycle import JobCancellationError
 from .notification import EmailError, NotificationError, WebhookError
@@ -18,8 +21,8 @@ __all__ = [
     "JobError",
     "ValidationError",
     "ConfigurationError",
-    "ConnectionError",
-    "TimeoutError",
+    "ServiceConnectionError",
+    "OperationTimeoutError",
     "ResourceNotFoundError",
     "DependencyError",
     "AuthenticationError",
@@ -34,3 +37,14 @@ __all__ = [
     "WebhookError",
     "JobCancellationError",
 ]
+
+#: Renamed in 0.2.0 because they shadowed Python builtins without inheriting
+#: from them. The alias is the same class object, so ``except`` keeps working.
+_DEPRECATED_ALIASES = {
+    "ConnectionError": ServiceConnectionError,
+    "TimeoutError": OperationTimeoutError,
+}
+
+
+def __getattr__(name: str) -> Any:
+    return resolve_deprecated(__name__, _DEPRECATED_ALIASES, name)

{dataexcept-0.1.0 → dataexcept-0.2.1}/dataexcept/exceptions/external.py

@@ -1,7 +1,7 @@
 from .base import JobError
 
 
-class ConnectionError(JobError):
+class ServiceConnectionError(JobError):
     """Raised when a connection to an external service fails."""
 
     def __init__(self, service_name: str, original_exception: Exception | None = None):
@@ -13,7 +13,7 @@ class ConnectionError(JobError):
         super().__init__(msg)
 
 
-class TimeoutError(JobError):
+class OperationTimeoutError(JobError):
     """Raised when an operation exceeds its time limit."""
 
     def __init__(self, operation: str, timeout: float):

{dataexcept-0.1.0 → dataexcept-0.2.1}/dataexcept/job_exceptions.py

@@ -1,9 +1,15 @@
 """Backward compatible job-related exceptions.
 
+.. deprecated:: 0.1.0
+    Use :mod:`dataexcept.exceptions` instead. This module is scheduled for
+    removal in 1.0.0; see the stability policy in the documentation.
+
 This module re-exports the core job exceptions defined in
-:mod:`dataexcept.exceptions`. Applications should import from that
-package directly going forward. Importing from :mod:`dataexcept.job_exceptions`
-will raise a :class:`DeprecationWarning`.
+:mod:`dataexcept.exceptions`. Importing it emits a :class:`DeprecationWarning`.
+Every name it exports is available from :mod:`dataexcept.exceptions` and from
+the top-level :mod:`dataexcept` package, so the migration is a change of import
+line only -- the classes are identical objects, not replacements, so existing
+``except`` clauses keep working during the transition.
 """
 
 from __future__ import annotations
@@ -14,7 +20,6 @@ from .exceptions import (
     AuthenticationError,
     AuthorizationError,
     ConfigurationError,
-    ConnectionError,
     CronExpressionError,
     DependencyError,
     DeserializationError,
@@ -22,15 +27,21 @@ from .exceptions import (
     JobCancellationError,
     JobError,
     NotificationError,
+    OperationTimeoutError,
     ParsingError,
     ResourceNotFoundError,
     ScheduleConflictError,
     SerializationError,
-    TimeoutError,
+    ServiceConnectionError,
     ValidationError,
     WebhookError,
 )
 
+# This module is itself deprecated, so it binds the pre-0.2.0 names directly
+# rather than going through the alias machinery and warning a second time.
+ConnectionError = ServiceConnectionError
+TimeoutError = OperationTimeoutError
+
 __all__ = [
     "JobError",
     "ValidationError",
@@ -53,7 +64,8 @@ __all__ = [
 ]
 
 warnings.warn(
-    "dataexcept.job_exceptions is deprecated; use dataexcept.exceptions instead",
+    "dataexcept.job_exceptions is deprecated and will be removed in 1.0.0; "
+    "use dataexcept.exceptions instead",
     DeprecationWarning,
     stacklevel=2,
 )

{dataexcept-0.1.0 → dataexcept-0.2.1}/dataexcept/logging_helpers.py

@@ -9,6 +9,13 @@ from typing import Any, Iterator, Mapping, Optional
 
 Context = Mapping[str, Any]
 
+__all__ = [
+    "Context",
+    "log_and_raise",
+    "log_exception",
+    "log_then_raise",
+]
+
 
 def _normalize_context_value(value: Any) -> Any:
     try:

{dataexcept-0.1.0 → dataexcept-0.2.1}/dataexcept/pipeline_exceptions.py

@@ -4,6 +4,8 @@ from __future__ import annotations
 
 from typing import Any, Optional
 
+from ._deprecation import resolve_deprecated
+
 
 class PipelineError(Exception):
     """Base exception for pipeline errors."""
@@ -22,7 +24,7 @@ class PreprocessingError(PipelineError):
         super().__init__(message)
 
 
-class FeatureEngineeringError(PreprocessingError):
+class FeaturePreprocessingError(PreprocessingError):
     """Raised when feature engineering fails."""
 
     def __init__(self, feature: str, reason: Optional[str] = None) -> None:
@@ -190,7 +192,7 @@ class DataFetchError(PipelineError):
 __all__ = [
     "PipelineError",
     "PreprocessingError",
-    "FeatureEngineeringError",
+    "FeaturePreprocessingError",
     "StorageError",
     "PipelineNotificationError",
     "RetryLimitExceededError",
@@ -203,3 +205,12 @@ __all__ = [
     "TypeCheckError",
     "DataFetchError",
 ]
+
+#: Renamed in 0.2.0: this named the same thing as
+#: ``dataexcept.datascience_exceptions.FeatureEngineeringError`` while being a
+#: different class, so catching one silently missed the other.
+_DEPRECATED_ALIASES = {"FeatureEngineeringError": FeaturePreprocessingError}
+
+
+def __getattr__(name: str) -> Any:
+    return resolve_deprecated(__name__, _DEPRECATED_ALIASES, name)

{dataexcept-0.1.0 → dataexcept-0.2.1}/pyproject.toml

@@ -1,24 +1,15 @@
-[tool.poetry]
+[project]
 name = "DataExcept"
-version = "0.1.0"
+version = "0.2.1"
 description = "A Python package providing structured, easily-extendable custom exception types."
-authors = ["Diogo Ribeiro <dfr@esmad.ipp.pt>"]
-maintainers = ["Diogo Ribeiro <diogo.debastos.ribeiro@gmail.com>"]
-license = "MIT"
 readme = "README.md"
-homepage = "https://github.com/DiogoRibeiro7/DataExcept"
-repository = "https://github.com/DiogoRibeiro7/DataExcept"
-documentation = "https://diogoribeiro7.github.io/DataExcept/"
-packages = [{ include = "dataexcept" }]
+license = "MIT"
+license-files = ["LICENSE"]
+requires-python = ">=3.10,<3.14"
+authors = [{ name = "Diogo Ribeiro", email = "dfr@esmad.ipp.pt" }]
+maintainers = [{ name = "Diogo Ribeiro", email = "diogo.debastos.ribeiro@gmail.com" }]
 keywords = ["exceptions", "errors", "logging"]
-include = [
-    "CITATION.cff",
-    "LICENSE",
-    "CHANGELOG.md",
-]
-
 classifiers = [
-    "License :: OSI Approved :: MIT License",
     "Programming Language :: Python :: 3",
     "Programming Language :: Python :: 3 :: Only",
     "Programming Language :: Python :: 3.10",
@@ -26,17 +17,26 @@ classifiers = [
     "Programming Language :: Python :: 3.12",
     "Programming Language :: Python :: 3.13",
 ]
+dependencies = [
+    "tomli ; python_version < '3.11'",
+]
 
-[tool.poetry.urls]
+[project.urls]
+Homepage = "https://github.com/DiogoRibeiro7/DataExcept"
+Repository = "https://github.com/DiogoRibeiro7/DataExcept"
+Documentation = "https://diogoribeiro7.github.io/DataExcept/"
 Changelog = "https://github.com/DiogoRibeiro7/DataExcept/releases"
 Issues = "https://github.com/DiogoRibeiro7/DataExcept/issues"
 
-[tool.poetry.scripts]
+[project.scripts]
 dataexcept = "dataexcept.__main__:main"
 
-[tool.poetry.dependencies]
-python = ">=3.10,<3.14"
-tomli = { version = "*", python = "<3.11" }
+[tool.poetry]
+packages = [{ include = "dataexcept" }]
+include = [
+    "CITATION.cff",
+    "CHANGELOG.md",
+]
 
 [tool.poetry.group.dev.dependencies]
 black = "*"
@@ -54,7 +54,7 @@ mkdocs-material = ">=9.5,<10"
 mkdocstrings = { extras = ["python"], version = ">=0.26" }
 
 [build-system]
-requires = ["poetry-core>=1.0.0"]
+requires = ["poetry-core>=2.0.0"]
 build-backend = "poetry.core.masonry.api"
 
 [tool.flake8]
@@ -72,9 +72,26 @@ line-length = 88
 target-version = "py310"
 
 [tool.ruff.lint]
-select = ["E", "F"]
+# S = flake8-bandit (security), C90 = mccabe (complexity). Both ship with ruff,
+# so neither needs a separate tool in CI.
+select = ["E", "F", "S", "C90"]
 ignore = []
 
+[tool.ruff.lint.mccabe]
+# The most complex function in the package currently scores 6. Eight leaves
+# room to breathe while still catching a function that grows out of hand.
+max-complexity = 8
+
+[tool.ruff.lint.per-file-ignores]
+# assert is how a test asserts, and "/tmp/data" there is a string literal used
+# as fixture data rather than a path that is ever opened.
+"tests/**" = ["S101", "S108", "S603"]
+# The lambda example asserts to narrow Optionals for the type checker.
+"examples/**" = ["S101"]
+# bump_version.py deliberately shells out to poetry, by name, on a maintainer's
+# own machine.
+"scripts/**" = ["S603", "S607"]
+
 [tool.mypy]
 python_version = "3.10"
 files = ["dataexcept"]

dataexcept-0.1.0/CHANGELOG.md

@@ -1,42 +0,0 @@
-# Changelog
-
-All notable changes to this project are documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [Unreleased]
-
-## [0.1.0] - 2026-08-24
-
-First public release.
-
-### Added
-
-- Hierarchical exception classes for data science, machine learning and data
-  engineering workflows. Catch a specific failure or a broad category, and get
-  a message that names the value that caused it rather than a bare
-  `ValueError`.
-- Domain modules for validation, configuration, authentication, parsing,
-  serialization, scheduling, notification, lifecycle and external-service
-  errors, plus dedicated pandas, database, network, I/O, pipeline and security
-  exception groups.
-- `dataexcept.logging_helpers` with `log_exception`, `log_and_raise` and
-  `log_then_raise`, for logging exceptions with structured context and
-  re-raising without losing the traceback.
-- A `dataexcept` command-line entry point that lists the exported exception
-  classes and reports the installed version.
-- A `py.typed` marker, backed by a mypy-clean codebase that CI enforces, so
-  downstream type checkers get annotations that are actually correct.
-- Documentation at
-  [diogoribeiro7.github.io/DataExcept](https://diogoribeiro7.github.io/DataExcept/),
-  including an API reference generated from the docstrings.
-
-### Notes
-
-- Supports Python 3.10 through 3.13.
-- Published to PyPI via OIDC trusted publishing; no long-lived API token is
-  involved in a release.
-
-[Unreleased]: https://github.com/DiogoRibeiro7/DataExcept/compare/v0.1.0...HEAD
-[0.1.0]: https://github.com/DiogoRibeiro7/DataExcept/releases/tag/v0.1.0