hunterhogan / hunterhogan/hunterMakesPy
"Evaluate When Packaging" and "Evaluate When Installing"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I strongly prefer dynamic values and dynamic handling of values. Nevertheless, some values should be static and universal. In my opinion, all of the values marked with "Evaluate When Packaging" and "Evaluate When Installing" should be 1) static and 2) easily accessible by any part of the package.
The two archetypical examples of Python values that are not easy to discover from within a package are the name of the package and the root directory of the package (relative or absolute).
I feel some values should be fixed when I, the developer, "package" the Python code and send it to PyPI. I believe a few more values should (usually) be fixed when the user installs the package.
The metadata markers metadata={'evaluateWhen': '...'} signal values that I believe should be static.
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
The issue names no files, tests, or entry points to inspect. Start by clarifying which metadata markers and package values are in scope, then define the expected packaging and installation behavior before implementation can be considered complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100