Last updated: 2026-10-04
This roadmap reflects current priorities.
The dated priority review (#566) records execution order and historical verification. Prioritize reproduced correctness failures as high, bounded verification and release preparation as medium, and optional compatibility extensions as low. Size estimates effort independently of urgency. Preserve existing contributor ownership and use one focused acceptance contract per PR.
The remaining larger work in the 2026-10-04 snapshot is:
| Order | Issue | Priority / size | Completion boundary |
|---|---|---|---|
| 1 | #634 — release-please integration audit | medium / L | Migration is integrated; reviewed candidate and publisher/recovery evidence remain separate. |
| 2 | #336 — adversarial verification audit | medium / XL | Reconcile actual runs, measurements and known limitations; passing child PRs do not complete the parent. |
| 3 | #610 — wrapper collection call shapes | low / M | Decide and verify the explicit compatibility contract before implementation. |
| 4 | #678 — positive-only fetch-size migration | low / M | Decided: deprecate in 1.x (DeprecationWarning, result unchanged), raise ProgrammingError in 2.0. The 2.0 step remains. |
Small release-preparation work is tracked by #371 (fetch-size validation) and #327 (runnable README examples). Their issue/PR records carry completion evidence. #675, the unfiled upstream CUBRID crash report, is excluded from this release-preparation scope and remains open. This snapshot is an index, not a claim that all issues are complete or that a release has passed its publication gates. Use the live open issue list for current status; dependencies govern completion, not investigation.
- Upstream Python 3.10 support ended on 2026-10-01 (PEP 619).
- 1.8.x and 1.9.x: Python >=3.10 is the installation requirement.
- 1.9.0 (published 2026-10-04): carried the advance notice in CHANGELOG Deprecated and the support matrix; Python 3.10 stays supported throughout the 1.9.x line.
- Done on
mainfor the next minor release (planned 1.10.0): package metadata requires Python >=3.11, the 3.10 classifier is removed and CI matrices start at 3.11 (#684). Tooling targets, 3.10-only code and the remaining documentation follow in the child issues of #682. - Users should migrate Python and recreate/test their virtual environment before upgrading to the removal release. No release date or publication is claimed.
- Supported from the next release (see the
[Unreleased]CHANGELOG section): classifier, full release matrix (Python 3.11–3.15 × CUBRID 10.2–11.4), 3.15 as the newest offline endpoint and English/Korean supported-version docs, tracked in cubrid-lab/sqlalchemy-cubrid#666. Standard GIL builds only; no free-threaded claim.requires-pythonstays>=3.11. - Preparation history: on 2026-10-03, 3.15.0rc3 was a preview
(upstream release notes).
A manually dispatched Ubuntu/standard-GIL preview lane (
python-canary.yml) checked offline regressions and fresh wheel/sdist installations; it is kept as a manual packaging check.
Current source version: pycubrid.__version__.
Published releases and dated history: CHANGELOG.
- Stable sync DB-API 2.0 surface plus native asyncio API (
pycubrid.aio) - Current async transport uses
asyncio.open_connection()withStreamReader/StreamWriter; seeaio/connection.py. - JSON / collection decoding,
ping(),nextset(), and sync + async TLS (TLS 1.2 minimum) - 1.x release policy enforced by an automated
compat-checkCI gate againstapi-baseline.json - Supported runtimes: Python 3.11–3.15 (3.10 until 1.9.x), CUBRID 10.2–11.4
See Completed for the per-release milestone history.
- Full CUBRID 12.x support
- Higher-level LOB helpers for fetched handles
- Prepared statement caching
Python 3.11+ (3.10 until 1.9.x), CUBRID 10.2–11.4
- 1.x release policy with an automated
compat-checkCI gate againstapi-baseline.json(v1.5.0) - Python 3.10 async-TLS preflight verification probe (v1.5.0)
- Python 3.14 support validated in CI (v1.6.2 baseline)
- Native
Connection.ping()via CHECK_CAS (FC=32) errno/sqlstateon allDatabaseErrorsubclasses- JSON type decoding (opt-in, protocol v8)
- Collection type decoding: SET/MULTISET/SEQUENCE (opt-in)
- Hardened parameter binding security
- Native asyncio API via
pycubrid.aiomodule AsyncConnectionandAsyncCursorwith full async/await support- Non-blocking socket I/O using
loop.sock_*
- Sync TLS via
ssl=Trueor customssl.SSLContext(v1.3.0) - Async TLS via
pycubrid.aio.connect(ssl=...)using CUBRID's STARTTLS-style upgrade (plaintextCUBRShandshake →loop.start_tls(); v1.4.0, corrected in #154) - Default TLS context enforces TLS 1.2 minimum (v1.4.0)
- Expanded Python 3.14 / CUBRID 10.2–11.4 CI coverage