Remove LocalBackend export from root __init__.py#548
Merged
Conversation
bradhilton
approved these changes
Feb 3, 2026
Contributor
|
@arcticfly are there examples that will need to be updated? |
Contributor
Author
Not unless you added one in the last two weeks, which is when we started exporting LocalBackend from the root. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On non-linux clients, importing ART currently causes a
ModuleNotFoundError: No module named 'torch'error because LocalBackend requires torch. Looks like LocalBackend was added to art/init.py a couple weeks ago, but we don't need it to be there. Users can instead import LocalBackend fromart.local.Changes
log_constant_metrics_wandb