[MNT] Address lapsed pytorch-tabnet dependency with warnings and migration guide[MNT] Address lapsed pytorch-tabnet dependency with warnings and migration guidefeat: handle lapsed tabnet dependency with warnings and migration guide#659
Open
SHIVANSH-ux-ys wants to merge 1 commit into
Conversation
Author
|
Hi @manujosephv, just a quick follow-up on this. I've addressed the TabNet dependency issues and included a migration guide as discussed. Whenever you have a moment, could you please approve the CI runs so we can make sure everything is passing on the build side? Happy to tackle any feedback once the tests are green. |
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
1 participant
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.
Summary
This PR addresses the lapsed maintenance status of the
pytorch-tabnetsoft dependency (Issue #611). It introduces proactive runtime warnings and a comprehensive migration guide to assist users in transitioning to more stable and actively maintained architectures.Rationale
As identified by the maintainers in Issue #611,
pytorch-tabnethas not received updates since early 2023. To ensure the long-term stability of the PyTorch Tabular ecosystem and protect users from future compatibility breaks with PyTorch/Lightning updates, a "soft" deprecation path is necessary. This PR implements this by notifying users at runtime and providing a clear path forward.Fixes
Fixes #611
Key Changes
FutureWarninginTabNetModel.__init__to notify users of the unmaintained dependency status.docs/migration_guides/tabnet_migration.mdwhich highlights modern, high-performance alternatives like GANDALF and FT-Transformer.README.mdandAvailable Modelssection to flag the TabNet status and link directly to the migration documentation.