You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is again a suggestion, and again refers to the Python part of the software.
There are dependency declarations and they are handled with automated package management solutions (check mark review checklist).
However, I noticed that the different installation instructions for Python result in deferentially useful sets of packages: A from-source installation gets me development relevant packages like pytest in addition to dependencies relevant for standard usage, a poetry-based installation gives me the Sphinx-dependencies necessary to build the docs in addition.
I would argue that standard users wouldn't need to run tests or build docs, but those inclined to contribute would. It would be cool if installations for both of these groups (standard users: just those dependencies that are relevant for using the tool; contributors: dependencies for testing and documentation building) would be easily possible, documented, and consistent across installation methods.
The text was updated successfully, but these errors were encountered:
This is again a suggestion, and again refers to the Python part of the software.
There are dependency declarations and they are handled with automated package management solutions (check mark review checklist).
However, I noticed that the different installation instructions for Python result in deferentially useful sets of packages: A from-source installation gets me development relevant packages like pytest in addition to dependencies relevant for standard usage, a poetry-based installation gives me the Sphinx-dependencies necessary to build the docs in addition.
I would argue that standard users wouldn't need to run tests or build docs, but those inclined to contribute would. It would be cool if installations for both of these groups (standard users: just those dependencies that are relevant for using the tool; contributors: dependencies for testing and documentation building) would be easily possible, documented, and consistent across installation methods.
The text was updated successfully, but these errors were encountered: