-
Notifications
You must be signed in to change notification settings - Fork 24.2k
[Ez][BE]: Make implicit subpackage explicit #153347
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
base: main
Are you sure you want to change the base?
[Ez][BE]: Make implicit subpackage explicit #153347
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/153347
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 1 New Failure, 1 Unrelated FailureAs of commit e1f0cc9 with merge base 01cbf5a ( NEW FAILURE - The following job has failed:
BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
Sure
While newer Python versions do support this, explicit namespace package helps more IDEs and other autocomplete features detect what are actually suppose to be modules a little bit easier.
cc @ezyang @SherlockNoMad @EikanWang @jgong5 @wenzhe-nrv