Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: polyorderbooks/python-sdk
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: docs/readme-markets-example
Choose a base ref
...
head repository: polyorderbooks/python-sdk
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 5 commits
  • 1 file changed
  • 2 contributors

Commits on Aug 5, 2026

  1. Merge pull request #2 from polyorderbooks/docs/readme-markets-example

    Document list_markets response shape in README
    polyorderbooks authored Aug 5, 2026
    Configuration menu
    Copy the full SHA
    65a5423 View commit details
    Browse the repository at this point in the history
  2. Add PyPI version and Python version badges to README.

    Signals that polyorderbooks is a published package on PyPI.
    
    Co-authored-by: Cursor <cursoragent@cursor.com>
    polyorderbooks and cursoragent committed Aug 5, 2026
    Configuration menu
    Copy the full SHA
    1973d20 View commit details
    Browse the repository at this point in the history
  3. Merge pull request #3 from polyorderbooks/docs/pypi-badges

    Add PyPI badges to README
    polyorderbooks authored Aug 5, 2026
    Configuration menu
    Copy the full SHA
    b40c462 View commit details
    Browse the repository at this point in the history

Commits on Aug 19, 2026

  1. Read bids and asks from snapshots, and document the shape.

    The quickstart asked for point["b"] and point["a"]. The API returns
    {t, bids, asks} per the OrderBookSnapshot schema, so those keys do not exist.
    Both lookups used .get(...) or [], so there was no error — the snippet printed
    "bid None ask None" while 15 bid and 26 ask levels sat in the response. A
    developer trying the SDK would conclude the archive has no depth, on a product
    whose whole point is full L2 depth.
    
    Verified against the live API:
    
      before:  bid=None  ask=None   levels=0/0
      after:   bid=0.19  ask=0.2    levels=15/26
    
    The README documented the markets response shape but never the books shape,
    which is largely why the wrong keys went unnoticed. Adds it in the same style,
    including that ladders are [price, size] best-first, that depth varies per
    snapshot, and that the list can be empty when a window has no captures.
    polyorderbooks committed Aug 19, 2026
    Configuration menu
    Copy the full SHA
    6ce6683 View commit details
    Browse the repository at this point in the history
  2. Merge pull request #5 from polyorderbooks/fix/orderbook-field-names

    Read bids and asks from snapshots, and document the shape
    polyorderbooks authored Aug 19, 2026
    Configuration menu
    Copy the full SHA
    52fd764 View commit details
    Browse the repository at this point in the history
Loading