Is your feature request related to a problem? Please describe.
Currently, we advise app developers not to list dependencies in the setup.py/pyproject.toml, but instead list them in the install.yml so that the tethys install command can install them with Conda. This limits app developers to the tooling provided by Tethys for managing dependencies. It also makes it more difficult to distribute your application as a packaged python library, because you can't use standard build tools like setuptools, poetry, etc.
Describe the solution you'd like
Deprecate the install.yml and move that information into the pyproject.toml, using standard fields for listing dependencies, and listing others options in a namespaced section for Tethys apps. Then update the tethys install command to parse the information out of the pyproject.toml
Is your feature request related to a problem? Please describe. Currently, we advise app developers not to list dependencies in the setup.py/pyproject.toml, but instead list them in the install.yml so that the
tethys installcommand can install them with Conda. This limits app developers to the tooling provided by Tethys for managing dependencies. It also makes it more difficult to distribute your application as a packaged python library, because you can't use standard build tools like setuptools, poetry, etc.Describe the solution you'd like Deprecate the install.yml and move that information into the pyproject.toml, using standard fields for listing dependencies, and listing others options in a namespaced section for Tethys apps. Then update the
tethys installcommand to parse the information out of the pyproject.tomlDescribe alternatives you've considered None
Additional context None