feat: add support for Python 3.13 and 3.14

[pcriadoperez]

Summary

Brings this fork up to date with sammchardy/python-binance master (a merge commit, ~90 upstream commits through v1.0.37) and adds Python 3.13 / 3.14 support on top of it.

Support matrix

• .github/workflows/python-app.yml — test matrix extended to ['3.8', '3.9', '3.10', '3.11', '3.12', '3.13', '3.14']
• tox.ini — envlist extended with py313, py314
• setup.py — added the Programming Language :: Python :: 3.13 / 3.14 classifiers

Code changes for 3.13 / 3.14

binance/helpers.py — get_loop()

On Python 3.14 asyncio.get_event_loop() no longer creates an event loop implicitly; it raises RuntimeError. The old implementation only recovered when the exception message started with "There is no current event loop in thread", which is a fragile contract to depend on. It also emitted a DeprecationWarning on 3.10–3.13 whenever it created a loop. The new version:

1. returns the running loop if there is one (asyncio.get_running_loop()),
2. otherwise falls back to the thread's current loop, ignoring the implicit-creation DeprecationWarning,
3. creates and sets a new loop when there is none, or when the current one is already closed.

binance/ws/threaded_stream.py — asyncio.iscoroutinefunction is deprecated in 3.14 and slated for removal in 3.16; switched to inspect.iscoroutinefunction.

binance/ws/websocket_api.py — removed an unused loop = asyncio.get_event_loop() in connection_lock; the value was never read, and the call itself raises on 3.14 when no loop is set.

examples/ — asyncio.get_event_loop() → asyncio.run(), and datetime.utcfromtimestamp(0).replace(tzinfo=...) → datetime.fromtimestamp(0, tz=...).

Verification

Ran against real 3.13.12 and 3.14.0rc2 interpreters, with 3.12.3 as the baseline.

• pip install -r requirements.txt -r test-requirements.txt resolves cleanly on both 3.13 and 3.14.
• Offline test subset (test_ids, test_init, test_cryptography, test_reconnecting_websocket, test_threaded_stream, test_error_propagation, test_verbose_mode, test_ws_urls_integration, test_websocket_verbose, test_depth_cache, test_socket_manager): 95 passed / 12 failed, identical on 3.12, 3.13 and 3.14 — no version-specific regressions.
• get_loop() exercised on all three versions with DeprecationWarning escalated to an error, covering: fresh main thread, repeat call reuses the same loop, call from inside a running loop returns that loop, a closed current loop is replaced, and a worker thread gets its own loop. All pass with no warnings.
• A DeprecationWarning sweep over the test run on 3.14 shows no remaining warnings originating from binance/ (the ones left come from aiohttp and websockets internals).
• ruff check --target-version=py39 . passes; pyright reports 0 errors.

Pre-existing failures (not introduced here)

The 12 failures above reproduce identically on 3.12, so they are unrelated to this change:

• 11 async tests in tests/test_ids.py fail with TypeError: ClientResponse.__init__() missing 1 required keyword-only argument: 'stream_writer' — aioresponses is not compatible with the current unpinned aiohttp release. This affects every Python version in the matrix and likely makes CI red on master today; fixing it means pinning a test dependency, which felt out of scope for this PR.
• tests/test_socket_manager.py::test_ticker_socket times out here because the sandbox has no outbound access to the Binance stream endpoints.

---

Generated by Claude Code

[pcriadoperez]

CI status: pushed one fix, two pre-existing blockers remain

The first CI run ended with test (3.8) failed and every other leg cancelled — including the 3.13 and 3.14 legs this PR exists to add, which never ran at all.

Fixed here: fail-fast: false (c59f952)

The test matrix had no fail-fast: false, so the first failing interpreter cancelled all the others. That made every matrix entry unevaluable the moment any single one broke. Added fail-fast: false so each version reports on its own merits.

Not fixed here: two pre-existing aioresponses problems

Both are independent of this diff — this PR touches only the CI matrix, tox envlist, classifiers, changelog, three binance/ modules and two examples. Neither can affect whether a test dependency imports.

1. aioresponses 0.7.9 does not support Python 3.8 — this is what broke the 3.8 leg:

aioresponses/core.py:131: in RequestMatch
    def _build_raw_headers(self, headers: Mapping[str, str]) -> Tuple:
E   TypeError: 'ABCMeta' object is not subscriptable

collections.abc.Mapping[str, str] in an annotation evaluated at class-body time needs PEP 585, i.e. Python 3.9+. Reproduced in a bare 3.8 venv containing only aioresponses — no repo code involved. 0.7.8 imports fine on 3.8.

Proposed patch for test-requirements.txt:

aioresponses<0.7.9; python_version < '3.9'

2. aioresponses 0.7.9 is incompatible with aiohttp >= 3.13 — this affects every Python version, and is almost certainly making master red today:

TypeError: ClientResponse.__init__() missing 1 required keyword-only argument: 'stream_writer'

requirements.txt leaves aiohttp unpinned, so CI resolves to 3.14.x and all 11 async tests in tests/test_ids.py fail. Proposed patch, also test-requirements.txt:

aiohttp<3.13

I've deliberately not pushed either one. Pinning aiohttp in the test environment means the suite stops exercising the aiohttp version your users actually get, which is a real trade-off and your call rather than something to slip into a Python-version PR.

Evidence that 3.13 and 3.14 themselves are fine

With aiohttp<3.13 installed locally (nothing else changed), against real 3.13.12 and 3.14.0rc2 interpreters, with 3.12.3 as the control:

	3.12.3	3.13.12	3.14.0rc2
tests/test_ids.py	22 passed	22 passed	22 passed
10-file offline subset	106 passed	106 passed	106 passed

Zero failures, identical on all three. The subset covers test_ids, test_init, test_cryptography, test_reconnecting_websocket, test_threaded_stream, test_error_propagation, test_verbose_mode, test_ws_urls_integration, test_websocket_verbose and test_depth_cache. Excluded only test_socket_manager, which needs outbound access to the Binance stream endpoints.

So the library changes in this PR stand on their own; what's left is a test-dependency decision that predates it and applies to the whole matrix.

---

Generated by Claude Code

[pcriadoperez]

CI now reports per-version, and 3.13 / 3.14 match the control exactly

With fail-fast: false in place, every leg ran instead of being cancelled. Results on c59f952, Id Tests step:

leg	interpreter	result
lint	3.9	passed
test (3.8)	3.8.18	failed — aioresponses needs 3.9+ (collection error)
test (3.10)	3.10.21	11 failed, 11 passed
test (3.11)	3.11.x	11 failed, 11 passed
test (3.12)	3.12.x	11 failed, 11 passed
test (3.13)	3.13.15	11 failed, 11 passed
test (3.14)	3.14.7	11 failed, 11 passed

3.10 through 3.14 are identical — same eleven test names, same stream_writer TypeError, nothing version-specific. 3.12 is the control: it was in the matrix before this PR and fails exactly the same way.

Two things this confirms for the versions this PR adds:

• actions/setup-python provisions 3.13.15 and 3.14.7 on ubuntu-22.04 without trouble — no runner-image or toolcache gap.
• pip install -r requirements.txt -r test-requirements.txt resolves and installs on both, binance imports, and the 11 sync tests in test_ids.py pass.

CI exercised 3.14.7 stable, which is better evidence than my local run (3.14.0rc2).

The remaining red is entirely the aioresponses situation described above, which stops every leg at Id Tests before tox -e py ever runs. The two proposed test-requirements.txt pins take the offline suite to 106/106 on 3.12, 3.13 and 3.14 locally; I'm leaving that call to you since pinning aiohttp for tests trades away coverage of the version users actually install.

---

Generated by Claude Code

[pcriadoperez]

Closing — this should target upstream instead

This PR was opened against pcriadoperez/python-binance:master. The change belongs upstream in sammchardy/python-binance, and GitHub does not allow changing a PR's base repository (only its base branch), so this one is being closed in favour of a fresh PR from this same branch to upstream.

The branch has been rebased onto sammchardy/python-binance@7d7b7fb (v1.0.37) so the upstream PR is clean:

• the merge commit is gone
• 6b9447f "add timeout to jobs" was dropped — upstream added the same timeout-minutes values independently, so it contributed zero diff against upstream
• what remains is two commits, 04e51f6 and f881b9d, touching 9 files

The resulting tree is byte-identical (d73b749) to c59f952, the commit CI validated on this PR — so the 3.13.15 / 3.14.7 results reported above still describe exactly this code.

Open the upstream PR here:
https://github.com/sammchardy/python-binance/compare/master...pcriadoperez:python-binance:claude/python-3.13-3.14-support-y5e369?expand=1

The analysis in the comments above (the two aioresponses blockers and their proposed patches) still applies and is worth carrying into the upstream discussion, since it affects the whole matrix on upstream master too.

---

Generated by Claude Code