User Story
As a Python developer maintaining this package,
I want the setup.py file to use semantic versioning
so that dependency management aligns with Python packaging standards and downstream tools can interpret versions correctly.
Background
The current version format "2025.4.171239" in setup.py violates PEP 440 standards, which:
- Prevents predictable version comparisons (e.g.,
pip install "eknowledge>=2025.4" fails)
- Conflicts with PyPI's semantic version expectations, risking future deployment issues
- Complicates automated dependency updates in CI/CD pipelines
The hardcoded version string in setup.py also lacks a clear release strategy. This directly impacts the PyPI badge URL in README.md, which currently references the non-compliant version.
Acceptance Criteria
User Story
As a Python developer maintaining this package,
I want the
setup.pyfile to use semantic versioningso that dependency management aligns with Python packaging standards and downstream tools can interpret versions correctly.
Background
The current version format "2025.4.171239" in
setup.pyviolates PEP 440 standards, which:pip install "eknowledge>=2025.4"fails)The hardcoded version string in
setup.pyalso lacks a clear release strategy. This directly impacts the PyPI badge URL inREADME.md, which currently references the non-compliant version.Acceptance Criteria
setup.pyto use a semantic version (e.g., "0.1.0") instead of "2025.4.171239"README.mdtohttps://badge.fury.io/py/eknowledge.svg?version=0.1.0version='0.1.0')python setup.py --versionand confirming semantic outputpip install -e .works without version parsing errors