This repository has been archived by the owner on Jul 9, 2021. It is now read-only.
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.
Based on my proposal in #29 (comment), I'd like to propose that
dask-lightgbm
have one more release, and that that release raise a warning on import informing users that the project is deprecated and that it has been merged intolightgbm
.I think this is preferable to just archiving the repo, because it means anyone upgrading
dask-lightgbm
in automationpip install
-ing it based on a Stack Overflow answer or blog post will get a warning nudging them towardslightgbm
.As of the changes in this PR, the following warning will be shown once per session, when you import this library.
python -c "import dask_lightgbm"
cc @jsignell @jrbourbeau
Thanks for your time and consideration.