-
Notifications
You must be signed in to change notification settings - Fork 39
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
refactor: Remove 'show_gui' from launch_fluent arguments. #2796
Conversation
Co-authored-by: Sean Pearson <93727996+seanpearsonuk@users.noreply.github.com>
Co-authored-by: Sean Pearson <93727996+seanpearsonuk@users.noreply.github.com>
Co-authored-by: Raphael Luciano <raphael.luciano@ansys.com>
Co-authored-by: Raphael Luciano <raphael.luciano@ansys.com>
Co-authored-by: Raphael Luciano <raphael.luciano@ansys.com>
for more information, see https://pre-commit.ci
argument.""" | ||
if old_arg in kwargs: | ||
warnings.warn( | ||
f"'{old_arg}' is deprecated. Use '{new_arg}' instead.", |
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.
At this point we will be automatically replacing the deprecated argument with the new one, right? So I think a more appropriate wording would be:
f"'{old_arg}' is deprecated. Use '{new_arg}' instead.", | |
f"'{old_arg}' is deprecated. Using '{new_arg}' instead.", |
And can we move val
definition before this warning, so that we can show it in the warning as well to better inform the user?
For example, putting these two suggestions together:
f"'{old_arg}' is deprecated. Use '{new_arg}' instead.", | |
f"'{old_arg}' is deprecated. Using '{new_arg} = {val}' instead.", |
Remove the ''show_gui'' argument and put a mechanism for migrating older scripts.