Skip to content

packaging: say which pyproject entries are django-marina only - #683

Merged
dyve merged 1 commit into
mainfrom
packaging-marina-only-entries
Sep 21, 2026
Merged

dyve merged 1 commit into
mainfrom
packaging-marina-only-entries

Conversation

@dyve

@dyve dyve commented Sep 21, 2026

Copy link
Copy Markdown
Member

PACKAGING.md says to copy [tool.check-manifest] ignore verbatim into every sibling, but this repo's copy carries a PACKAGING.md entry, and so does source-exclude in [tool.uv.build-backend]. That file exists only here, so following the instruction literally would leave every sibling with a rule for a file it does not have.

All four siblings already omit both entries, so there is nothing to propagate. This just writes down what they already do, before someone syncs the list verbatim and adds dead configuration. The paragraph is also split in two, because the pyproject.toml.orig rationale had nothing to do with the sentence it was attached to.

🤖 Generated with Claude Code

PACKAGING.md said to copy [tool.check-manifest] ignore verbatim, but this
repo's copy carries a PACKAGING.md entry, and so does source-exclude in
[tool.uv.build-backend]. The file exists nowhere else, so following the
instruction literally would have every sibling ignore a file it does not have.

The four siblings already omit both entries, so nothing needs propagating. This
only writes down what they already do, before someone syncs the list verbatim
and adds dead configuration.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@dyve
dyve merged commit 4c3bdd9 into main Sep 21, 2026
21 checks passed
@dyve
dyve deleted the packaging-marina-only-entries branch September 21, 2026 07:09
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.

1 participant