Open
Description
Problem Statement
We shouldn't have to have repeat project metadata files, both pyproject.toml and viper.toml files.
The config should also be able to work without any site setup by just using the project's config if a site config doesn't exist. The "site config" should be contained in the folder above the project.
Proposed Solution
Since Viper packages are Python packages, we should have the option of including the metadata as part of the pyproject.toml config file.
The viper specific items would be included under the tools.viper table
Alternatives Considered
Proposed Action Plan
- 1. Update the config to read the project.toml
- 2. We'll do that
- 3. Then we'll add tests for this and that.