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
it'd be nice if I only had to specify my library's dependencies in [edgetest.envs.core] instead of needing to remember to add every new test dependency. there's already a considerable amount of env declaration duplication required throughout the various package managing tools, so it'd be nice if there wasn't another layer of duplication here
I'd like to only need to specify the libraries I want to try updating in [edgetest.envs.core]. I'd like to inherit the rest of the dependencies from an environment file. for example:
for context, Shania has been adding new examples that get tested during our test suite. these examples can have a number of dependencies that aren't actual rubicon dependencies and we've been forgetting to add them to the edgetest config too, resulting in fails the next night
@ryanSoley I'll circle around this when @ak-gupta is back from vacation. I think it would be nice to specify a file, could just be something like conda_install_yaml in addition to conda_install or something along those lines.
it'd be nice if I only had to specify my library's dependencies in
[edgetest.envs.core]
instead of needing to remember to add every new test dependency. there's already a considerable amount of env declaration duplication required throughout the various package managing tools, so it'd be nice if there wasn't another layer of duplication hereI'd like to only need to specify the libraries I want to try updating in
[edgetest.envs.core]
. I'd like to inherit the rest of the dependencies from an environment file. for example:The text was updated successfully, but these errors were encountered: