Checklist
What is the idea?
Currently noarch: python recipes (both v0 and v1) require including a list of entry_points: manually. However, the respective packages already carry the upstream list of entry points in the *.dist-info/entry_points.txt file.
The idea (as initially discussed with @jaimergp) would be to change the entry_points for noarch: python packages to allow three kinds of values:
- an explicit list of entry points (the current behavior)
true to automatically discover entry points from entry_points.txtfalse to disable automatic discovery and not create any entry points
Why is this needed?
The current behavior of having to manually "copy" entry_points is both cumbersome and carries a potential of missync if people miss changing entry points upstream.
What should happen?
No response
Additional Context
I may be missing something non-obvious as to why this wouldn't work.
Checklist
What is the idea?
Currently
noarch: pythonrecipes (both v0 and v1) require including a list ofentry_points:manually. However, the respective packages already carry the upstream list of entry points in the*.dist-info/entry_points.txtfile.The idea (as initially discussed with @jaimergp) would be to change the
entry_pointsfornoarch: pythonpackages to allow three kinds of values:trueto automatically discover entry points fromentry_points.txtfalseto disable automatic discovery and not create any entry pointsWhy is this needed?
The current behavior of having to manually "copy"
entry_pointsis both cumbersome and carries a potential of missync if people miss changing entry points upstream.What should happen?
No response
Additional Context
I may be missing something non-obvious as to why this wouldn't work.