Messages.parse (and AsyncMessages.parse) don't take cache_control?

Open Beginner friendly
#1,907 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api

Research direction

Start at the Messages.parse and AsyncMessages.parse entry points, then compare their parameters with Messages.create and Messages.stream. Verify the intended cache_control behavior and update the relevant SDK tests or documentation so the supported interface and its expected behavior are clear.

Written by the indexing model from the issue text.

Description

Messages.parse generally follows the API of Messages.create (and .stream), but is lacking the cache_control parameter. I don't see any obvious reason why that would be so perhaps it was just missed. But in case it is intentional I'd like to understand why.

Dominant language
Python
Stars
3.9k
Forks
857
Avg merge
1d 2h
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anthropics/anthropic-sdk-python

All issues in anthropics/anthropic-sdk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.