Skip to content

Releases: PythonSpring/pyspring-core

v0.0.4

03 Oct 04:35
Compare
Choose a tag to compare

py_spring_core v0.0.4 Release Notes

Version: v0.0.4

Release Date: 2024-10-03

Changelog:

New Additions:

  • PyPI Publishing Workflow: Implemented and added the PyPI publishment workflow. This introduces an automated publishing process to facilitate easier deployments to PyPI.

Packaging Refactor:

  • Package Renamed: The project structure has been refactored, and the package was renamed from py_spring to py_spring_core.
    • Deleted unused files and directories, including py_spring/__init__.py.
    • Updated the dynamic versioning in py_spring_core/__init__.py by referencing __version__.
    • Moved and renamed relevant files to the py_spring_core module.

Initial Version:

  • The initial version for the py_spring_core package has been set to 0.0.4.

Notes:

This release primarily focuses on project restructuring, packaging adjustments, and the introduction of the PyPI publishment workflow. No new features have been added, but there is a clearer organization for future development and a more efficient release process.

v0.0.2

02 Oct 09:11
Compare
Choose a tag to compare

Release Notes for v0.0.2

Type Hints Checker Enhancements

  • Type Hint Checker for ApplicationContext:

    • Introduced a dedicated type hint checker for the ApplicationContext, ensuring type correctness and improving developer confidence when handling application-wide dependencies. (commit: d39548e)
  • Type Hints Checking for Callable Functions:

    • Added support for validating type hints in callable functions, reinforcing strict type adherence for function inputs and outputs. (commit: 23ed469)
  • Refactor: Type Hint Checks:

    • Refactored the implementation of type hint checking for callable functions and classes, simplifying the codebase and enhancing the efficiency of type validation. (commit: 6d3a40d)

This update significantly improves type safety through robust type hint validation, ensuring that all callable functions and application contexts adhere to the expected type contracts.