Skip to content

Conversation

@blainekasten
Copy link
Contributor

No description provided.

@linear
Copy link

linear bot commented Nov 19, 2025

ENG-48363 Make Python finetuning create custom coded and not Stainless controlled

A decision with the fine tuning team is that we should preserve the previous logic for the fine-tuning create logic for Python.

The action steps here are:

  1. add skip: python to the fine_tuning.create spec in the Stainless.yml
  2. Copy the code over from together-python into together-py on the next branch

@blainekasten blainekasten force-pushed the blaine/eng-48363-make-python-finetuning-create-custom-coded-and-not-stainless branch 4 times, most recently from 0f4d72b to 284c534 Compare November 20, 2025 16:33
@blainekasten blainekasten force-pushed the blaine/eng-48363-make-python-finetuning-create-custom-coded-and-not-stainless branch 2 times, most recently from 33bbf49 to ac0b129 Compare November 20, 2025 16:43
@blainekasten blainekasten force-pushed the blaine/eng-48363-make-python-finetuning-create-custom-coded-and-not-stainless branch from ac0b129 to 48eb2a3 Compare November 20, 2025 16:58
# object type
object: Literal["fine-tune-event"]
# created at datetime stamp
created_at: Union[str, None] = None

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not necessary to change it, I can do it later in another PR.

  1. Should we switch str | None here?
  2. Do we want to support 3.9 or we can switchto >= 3.10?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may be a question for us to discuss with Stainless. All of their generated types use this Syntax so there may be a reason.

Do you have an opinion on supporting 3.9 or not?

@blainekasten blainekasten merged commit ef3bd52 into next Nov 21, 2025
9 checks passed
@stainless-app stainless-app bot mentioned this pull request Nov 21, 2025
blainekasten added a commit that referenced this pull request Nov 21, 2025
* chore(api): Remove auto-generated fine_tuning.create method from Python SDK

* feat(api): Change image creation signature to `images.generate`

BREAKING CHANGE: For the TS SDK the `images.create` is now `images.generate`

* feat(api): Change fine tuning download method to `.create`

BREAKING CHANGE: Change Fine Tuning method name from `download()` to `content()` to align with other namespaces

* feat(api): api update

* feat(api): Change rerank method signature

BREAKING CHANGE: Update method signature for reranking to `rerank.create()`

* feat(api): Port finetuning create code from together-python (#176)

* chore: Fix examples

* release: 2.0.0-alpha.1

---------

Co-authored-by: stainless-app[bot] <142633134+stainless-app[bot]@users.noreply.github.com>
Co-authored-by: Blaine Kasten <blainekasten@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants