-
Notifications
You must be signed in to change notification settings - Fork 4
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: run post_setup script on init #87
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.
left comments
multiworld/__init__.py
Outdated
|
||
try: | ||
post_setup.main() | ||
except Exception as e: |
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.
please remove this try-except statements. This simply catches the error but doesn't stop the script. This can cause confusion.
The two lines here(https://github.com/cisco-open/pymultiworld/blob/main/pyproject.toml#L16-L17) should be removed. |
https://github.com/cisco-open/pymultiworld/blob/main/multiworld/__main__.py file is also not needed any more. Please remove it. |
made changes to that post_setup script is executed in __init__.py of multiworld error handlers were while executing the main method. with the first execution, the patch is applied and the user is prompted to re-run the script to have the patched version of torch
6fd6bbe
to
7d833d5
Compare
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.
lgtm
made changes to that post_setup script is executed in init.py of multiworld error handlers were while executing the main method. with the first execution, the patch is applied and the user is prompted to re-run the script to have the patched version of torch
Description
Please provide a meaningful description of what this change will do, or is for. Bonus points for including links to
related issues, other PRs, or technical references.
Note that by not including a description, you are asking reviewers to do extra work to understand the context of this
change, which may lead to your PR taking much longer to review, or result in it not being reviewed at all.
Type of Change
Checklist