Skip to content

Releases: hermanzhaozzzz/pytdxfeed

pytdxfeed 1.0.2

Choose a tag to compare

@github-actions github-actions released this 22 Jul 13:29

Full Changelog: v1.0.1...v1.0.2

pytdxfeed 1.0.1

Choose a tag to compare

@hermanzhaozzzz hermanzhaozzzz released this 21 Jul 07:53

pytdxfeed 1.0.1 is a patch release for local tdx-api reliability.

Fixed:

  • Loopback requests now ignore environment HTTP proxy settings, so calls to 127.0.0.1 cannot be redirected to an unavailable proxy.
  • A correctly deployed managed tdx-api is allowed to recover through its LaunchAgent after transient health failures without asset reinstallation or forced redeployment.
  • Recovery failures retain explicit launchctl state, underlying errors, and stderr diagnostics.

Validation:

  • 26 tests passed on Python 3.11.
  • Ruff lint and format checks passed.
  • Wheel and source distributions passed Twine metadata validation.

Release artifacts:

  • pytdxfeed-1.0.1-py3-none-any.whl
  • pytdxfeed-1.0.1.tar.gz

pytdxfeed 1.0.0

Choose a tag to compare

@hermanzhaozzzz hermanzhaozzzz released this 21 Jul 07:37

pytdxfeed 1.0.0 is the first public release of the strict Python client and macOS lifecycle manager for the bundled local tdx-api service.

Highlights:

  • Manages one pinned tdx-api service through the per-user macOS LaunchAgent while preserving the fixed 127.0.0.1 host contract.
  • Supports explicit local ports, strict service ownership, arm64 and x86_64 bundled artifacts, and shared use by multiple consumers.
  • Waits for a correctly deployed managed service to recover after transient health failures without reinstalling or restarting it.
  • Bypasses environment HTTP proxies for loopback requests, preventing 127.0.0.1 health and market-data calls from being redirected to a proxy.
  • Provides strict stock K-line, index K-line, batch quote, recent trade, and service health APIs with observable failures and no data-source fallback.

Release artifacts:

  • pytdxfeed-1.0.0-py3-none-any.whl
  • pytdxfeed-1.0.0.tar.gz

Full documentation is available in README.md and README_zh.md.