Python 3.14 compatible mcp-contextforge-gateway library

[parban-lm]

Hi ,

when will we get the python 3.14 compatible mcp-contextforge-gateway library.

[Yigtwxx]

There's no announced date that I can find. What's there in the repo right now:

pyproject.toml on v1.0.8 pins

requires-python = ">=3.12,<3.14"

That's a hard upper bound, not just a missing classifier, so pip and uv will refuse to resolve the package on 3.14 rather than installing and failing later. The classifiers agree: they stop at Programming Language :: Python :: 3.13.

Worth knowing that the tested surface is narrower still. .github/workflows/pytest.yml runs the suite against a single version:

matrix:
  python: ["3.12"]

So 3.13 is permitted by the constraint but not covered by CI. If you want the version with the most evidence behind it, that's 3.12.

The tracking issue for 3.14 is #1638, opened in December, titled "Migrate to Python 3.14 with Free-Threading (No GIL)". It's still open, has no milestone, and the body labels the status as Experimental. It's scoped around free-threading and PEP 703 performance work rather than plain 3.14 compatibility, so I'd read it as exploratory rather than a scheduled port. Subscribing to it is probably the best signal you'll get.

If you're blocked today, the practical options are running the gateway on 3.12 in its own venv or container while the rest of your stack stays on 3.14, or building from a fork with the bound relaxed to <3.15 and running the suite yourself to see what actually breaks. Would be useful to post here if you try the second one, since nobody seems to have reported what fails yet.

[cafalchio]

Hi @parban-lm we do not have a timeline for it yet, we have just removed 3.11 from the supported versions and we should start to experiment with Python 3.14 in the near future.