petals/src/petals/client/__init__.py

from petals.client.config import ClientConfig
from petals.client.inference_session import InferenceSession
from petals.client.remote_sequential import RemoteSequential
from petals.client.routing import NoSpendingPolicy, RemoteSequenceManager, SpendingPolicyBase
Move SequenceManagerConfig -> ClientConfig, petals.dht_utils -> petals.utils.dht (#463) 10 months ago			`from petals.client.config import ClientConfig`
Make Petals a pip-installable package (attempt 2) (#102) 1. Petals can be now installed using `pip install git+https://github.com/bigscience-workshop/petals` - In case if you already cloned the repo, you can do `pip install .` or `pip install .[dev]` 2. Moved `src` => `src/petals` - Replaced `from src.smth import smth` with `from petals.smth import smth` 3. Moved `cli` => `src/petals/cli` - Replaced `python -m cli.run_smth` with `python -m petals.cli.run_smth` (all utilities are now available right after pip installation) 4. Moved the `requirements*.txt` contents to `setup.cfg` (`requirements.txt` for packages is not supported well by modern packaging utils) 5. Increased the package version from `0.2` to `1.0alpha1` 2 years ago			`from petals.client.inference_session import InferenceSession`
Refactor RemoteSequenceManager (#309) This PR: 1. Extracts `SequenceManagerConfig` and `SequenceManagerState` subclasses. The config is provided by caller and never changed from inside `RemoteSequenceManager`. The state is a part of the `RemoteSequenceManager`'s state shared between the main manager and its slices. We fix some slicing bugs along the way. 2. Removes `dht_prefix` and `p2p` arguments, makes `dht` argument optional. `dht_prefix` can always be overridden using `config.dht_prefix`. `p2p` actually needed only under the hood of `RemoteSequenceManager`, so it can extract it by itself without exposing this low-level class to callers. If strictly necessary, a caller can provide `p2p` as a part of `SequenceManagerState`. `dht` is also needed only by `RemoteSequenceManager`, so we can make it optional in the parent classes and create it automatically when it's not provided. 3. Simplifies retry logic. Previously, we could have "nested" retry loops: one in `._update()`, another in inference/forward/backward steps. The loop in `._update()` could introduce issues to concurrent inference/forward/backward calls, since it blocks the entire class if its delay period becomes too high. Now this logic is simplified: `._update()` performs only one attempt to fetch the DHT info, any retries are triggered by the inference/forward/backward steps. 4. Removes deprecated `RemoteTransformerBlock`. `RemoteTransformerBlock` was deprecated a long time ago, before Petals 1.0.0. Its removal is long due. 5. Removes `dht_utils.get_remote_module()`, `dht_utils.get_remote_sequence()`. This functions duplicate the functionality of the `RemoteSequential` constructor. 6. (minor) Removes `RemoteSequential.is_subsequence` flag. This flag worked incorrectly and was never used. I am removing it for the sake of simplicity. 1 year ago			`from petals.client.remote_sequential import RemoteSequential`
Move SequenceManagerConfig -> ClientConfig, petals.dht_utils -> petals.utils.dht (#463) 10 months ago			`from petals.client.routing import NoSpendingPolicy, RemoteSequenceManager, SpendingPolicyBase`