ansys / ansys/pyansys-dev-guide
Package dependency guidelines
Open
- Dominant language
- No language data
- Stars
- 41
- Forks
- 9
- Avg merge
- 11h 24m
- Merged PRs (30d)
- 12
Description
Coming from https://github.com/ansys/pyansys/pull/842#issuecomment-2637878870 we realized that this information is not published anywhere. We should clarify better how packages should handle dependencies for various purposes - just like @greschd outlined there.
Contributor guide
Research direction
Read the linked pyansys pull request comment first to capture the dependency guidance attributed to @greschd, then inspect the developer guide's existing documentation structure. Document how packages should handle dependencies for the purposes described there, and verify that the guidance is published in an appropriate guide section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100