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
I suggest a method be implemented to check for and update dependencies for examples. Since the examples are very broad and general, it does not make sense to include all dependencies for all examples. Instead, one might create a list of packages (or dict with package name as the key and version string as the value) and pass that dict to a function that will update the local Python environment.
I'm not too favorable with this approach for multiple reasons. Some can be argued as we provide example ourselves and control everything but for others I have concerns:
version control can't be achieved with that approach and new version of a package could be incompatible with the code
executing subprocess calls can present security issues (arguable since we control the code of the examples)
portability might be an issue as every user might have a different python configuration (arguable)
separating preoccupations about up dependencies update and code execution
However, it might make sense to gather dependencies groups for specific folders / group of examples. We would have additional targets (like we have for [doc] or [tests]). @dcrawforAtAnsys What do you think ?
📝 Description of the feature
I suggest a method be implemented to check for and update dependencies for examples. Since the examples are very broad and general, it does not make sense to include all dependencies for all examples. Instead, one might create a list of packages (or dict with package name as the key and version string as the value) and pass that dict to a function that will update the local Python environment.
💡 Steps for implementing the feature
The example could then look like:
The code from the EMIT example could be used as a reference to create the
check_packages()
function:🔗 Useful links and references
No response
The text was updated successfully, but these errors were encountered: