README cleanup: trim icons, collapse BibTeX, soften pricing, footer#277
Conversation
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
There was a problem hiding this comment.
Code Review
This pull request removes the 'License', 'Development', and 'Release' sections from the README.md file. The reviewer noted that these sections contain vital information for contributors and maintainers regarding environment setup and the release process, and recommended retaining them or moving them to a separate file like CONTRIBUTING.md.
I am having trouble creating individual review comments. Click here to see my feedback.
README.md (204-271)
The removal of the 'License', 'Development', and 'Release' sections significantly reduces the documentation available for contributors and maintainers. These sections contain vital information regarding the project's licensing, environment setup (ruff, pre-commit), and the release process. If these details are being moved to a separate file (e.g., CONTRIBUTING.md), please ensure that file is included in this pull request. Otherwise, it is recommended to retain these sections to maintain project transparency and ease of contribution.
Matches the treatment in PriorLabs/TabPFN#954. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Drops the ✅/🌐/🏁/🔑/🤝/📊/📚 icons from the section headers. - Adds the TabPFN-2.5 bibtex entry + intro line so Citation matches the canonical version in PriorLabs/TabPFN. - Removes the Best Results subsection (extensions advice belongs in the TabPFN repo / docs, not the client). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Drops the explicit pricing formula in favour of a qualitative description so the README isn't load-bearing for the v3 formula constants. Updates the limits to the new defaults (50M daily, 200M monthly) and points at the live usage page rather than just response headers. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The original PR pruning accidentally dropped the License section alongside the Development/Release blocks. License (Apache 2.0) is genuine user-facing info and should stay. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Matches the convention used in PriorLabs/tabpfn-extensions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Limits change server-side independently of releases; the live usage page is now the source of truth. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
brendan-priorlabs
left a comment
There was a problem hiding this comment.
Can you please keep the release stuff? I use that all the time
|
Release stuff should live somewhere internal, I'll add it back and we think of where it should go next |
Per review feedback: the build-from-source and pypi-release instructions are useful and should stay, but they don't belong inline in the public README. Tucking them behind a single <details> toggle keeps the top-level README scannable while preserving the content. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
brendan-priorlabs
left a comment
There was a problem hiding this comment.
Thank you! Yes, agreed
README cleanup for the client. No code changes.
<details>toggle under## Development. Content (pre-commit setup, build-from-source, PyPI release flow) is preserved verbatim; just hidden behind a click so the top-level README stays scannable.<details>toggle in the Citation section so it doesn't dominate the page when expanded.PriorLabs/TabPFN: adds the missinggrinsztajn2025tabpfn(TabPFN-2.5 model report) entry plus the intro sentence linking both papers. Client previously only had the Nature paper + the original ICLR 2023 paper.Access/Delete Personal InformationtoAccess/Delete Data.PriorLabs/tabpfn-extensions.