Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

Status Update

• See: [Bug]: Unable to install OpenRAG using Python 3.12.3 due to explicit version check and requirement for Python 3.13 #1023 (comment)

@edwinjosechittilappilly

This is an pyproject of sdk and not of openrag itselt. is this an expected change.

• Yes, that is correct. Expected.
• Change is to do the following:
  • Add "Programming Language :: Python :: 3.13" classifier to sdks/mcp/pyproject.toml to match its requires-python = ">=3.10" range, which already included 3.13
• This also aligns with the main pyproject .toml file
  • However, the minimum version is more strict and enforced

[project]
name = "openrag"
version = "0.2.5"
...
requires-python = ">=3.13"

if so can you check the sdk pyproject also?

@edwinjosechittilappilly

if so can you check the sdk pyproject also?

• ✅ Done
• ✅ All 3 pyproject.toml files (main app, SDK, MCP) have been brought into alignment with respect to the specified classifiers
• ✅ Renamed PR summary and description to reflect the current changes

About Python Classifiers

• Classifiers are purely metadata
  • i.e. They have no effect on installation, dependency resolution, or runtime behaviour whatsoever.
• They are read-only labels that get uploaded to PyPI when the package is published.

What Python Classifiers Actually Do

• (a) PyPI search and filtering.
  • When someone browses https://pypi.org or uses tools like pip search, classifiers are used to filter and categorize packages.
    • e.g. Programming Language :: Python :: 3.13 makes the package appear in searches filtered to Python 3.13.
• (b) Tooling signals
  • Some tools (IDEs, dependency auditors, compatibility checkers) read classifiers to understand what environments a package officially supports.
• (c) Human communication.
  • They tell developers at a glance what the package supports without reading the full documentation.

What Python Classifiers Do NOT Do

• Does not enforce version compatibility (that's requires-python's job)
• Does not affect which wheel gets installed
• Does not affect uv/pip resolution in any way
  • e.g. A package with no 3.13 classifier will still install on Python 3.13 if requires-python allows it