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
{{ message }}
This repository has been archived by the owner on Oct 25, 2019. It is now read-only.
Currently we are using ENV to store the locations of all interpreters for solutions. It has been suggested that moving forward a config file would be a more flexible solution.
The text was updated successfully, but these errors were encountered:
ok so bench currently has a config file, the format has changed since the last time i pushed but it will now allow us to start packing more info based on the keyword. Bench still does not even bother with env vars, should this be added back in?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently we are using ENV to store the locations of all interpreters for solutions. It has been suggested that moving forward a config file would be a more flexible solution.
The text was updated successfully, but these errors were encountered: