generated from alvarobartt/python-package-template
-
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
003f775
commit 17fb2d0
Showing
1 changed file
with
10 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
## 🔮 TODOs | ||
|
||
- [ ] Add some working examples under `examples/` | ||
- [ ] Add custom `logging` messages within the `__init__` and `deploy` methods, skipping the `google-cloud-aiplatform` and any other logs already there | ||
- [ ] Add support for models available locally (provided via `model_name_or_path` but without having to call `snapshot_download`) | ||
- [ ] Handle logic within `TransformersModel` when `HF_HUB_ID` is within `environment_variables` and neither `model_name_or_path` nor `model_bucket_uri` have been provided | ||
- [ ] Add some more flags in case the user wants to specify the target bucket in Google Cloud Storage and the target repository in Google Artifact Registry | ||
- [ ] Handle the possible / supported values for the different `--build-args` provided to the Docker image | ||
- [ ] Add flag `experimental` to bypass the predefined checks / untested stuff in case users want to experiment further with the package without the limitations | ||
- [ ] Should we allow custom Docker images or just provide the optimized and supported ones? On the same topic, should we upload some of those pre-built to the Docker Hub so that those can be pulled from there instead of being built every single time locally? |