switch to pyproject.toml - #4235
Conversation
…cally reading requirements-minimal.txt and just inline the contents to fix the build
| ] | ||
|
|
||
| [project.optional-dependencies] | ||
| dev = [ |
There was a problem hiding this comment.
we should have the contents of requirements-dev-minimal here
| "virtualenv==20.36.0", | ||
| "zake==0.2.2", | ||
| ] | ||
| docs = [ |
There was a problem hiding this comment.
(this one will probably be harder to deal with, but this should also just have top-level deps)
There was a problem hiding this comment.
curious to see how we handle the yelpy reqs: in my head i've been mulling an approach where we have two pyproject.tomls and 2 poetry.locks + wrappers everywhere to ensure that the right pair is used
(since unless things have changed/i was misunderstanding things last time i looked into this, poetry has no config options and will always look for pyproject.toml/poetry.lock -- and last i looked, i didn't see a good way to handle the internal/external pypi config)
Resolved conflicts in setup.py by keeping the minimal version that just handles scripts alongside pyproject.toml. Updated pyproject.toml dev dependencies to use top-level deps only (from requirements-dev-minimal.txt) instead of pinned transitive deps, addressing PR feedback. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Since we're moving to pyproject.toml for dependency management, remove the check-requirements step which depends on requirements-minimal.txt. Update AGENTS.md to reflect the new dependency management approach using pyproject.toml instead of requirements-tools. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
I'm cooling on the idea of this PR, probably not worth reworking this stuff unless we go all the way to Poetry |
2 participants
No description provided.