-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QA Application Support #46
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks excellent. a couple of minor things.
If the QA executable exists within the current environment, but is not | ||
set with execute permissions for the current process. | ||
|
||
""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very clear docstring with just enough detail
""" | ||
command_line = [] | ||
|
||
if executable_path := shutil.which(qa_program_path): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked at PEP 572 - Assignment Expression and under Syntax and semantics I found an example of a regex that is pretty similar to what is here.
I think it's a little clearer to say:
if (executable_path := shutil.which(qa_program_path)) is not None:
f"but does not have execute permissions.") | ||
# Otherwise, qa_program_path might be a python module path | ||
else: | ||
command_line = ['python3', '-m', qa_program_path] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the comments here.
QA application execution is performed similarly to the main SAS execution, but is optional based on how the RunConfig is defined
4190588
to
81cc242
Compare
This PR updates the base PGE functionality to support execution of an optional Quality Assurance (QA) application after the primary SAS executable has completed. Execution occurs similarly to SAS execution, but is optional based on a setting within the RunConfig.