Skip to content

Fix entry points export (setup-to-pyproject) - #397

Open
gforcada wants to merge 6 commits into
2.xfrom
387-fix-entry-points
Open

Fix entry points export (setup-to-pyproject)#397
gforcada wants to merge 6 commits into
2.xfrom
387-fix-entry-points

Conversation

@gforcada

@gforcada gforcada commented Aug 1, 2026

Copy link
Copy Markdown
Member

Closes #387

@gforcada
gforcada requested a review from mauritsvanrees August 1, 2026 15:27
@gforcada
gforcada force-pushed the 387-fix-entry-points branch 2 times, most recently from 61a1231 to b941ec1 Compare August 2, 2026 06:10
Do not write back to `setup.py` the `long_description` kwarg,
as in general it writes README's and CHANGES' content,
breaking the code.
To keep `main` a bit more minimal.
As `key_buffer` was inside the loop, the entry points header,
which looks like `[entry-point-name]` was always lost on next iteration
before it could be safed on `ep_data`.
Use `plone.autoinclude` rather than old `z3c.autoinclude`.
@gforcada
gforcada force-pushed the 387-fix-entry-points branch from b941ec1 to 4205cb5 Compare August 2, 2026 13:28
@gforcada gforcada added the 01 type: bug something does not work label Aug 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

01 type: bug something does not work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

entry points are forgotten on setup.py to pyproject.toml

1 participant