python / python/importlib_metadata
Tighten the EntryPoint interface
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 142
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
I've also observed that the issue affects
.moduleand.attrand.load. I'm trying to decide what's the best behavior here. I think it should fail early, at construction time, but right now, the interface is open to mutation of the entry point properties. Probably those should be madefinal.
Originally posted by @jaraco in #488
Additionally, EntryPoint could probably subclass SimpleNamespace except that EntryPoint currently allows for positional arguments. Let's deprecate that behavior and require keyword arguments.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the EntryPoint definition and inspect its current construction and mutation behavior. Use the proposed final properties, keyword-only construction, and positional-argument deprecation as acceptance criteria; done requires the interface behavior and deprecation policy to be settled and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100