remove deprecation warning, platformdirs won't become default #447
Conversation
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
Back off plan to deprecate longstanding default paths
minrk
changed the title
This was referenced Oct 13, 2025
Carreau
reviewed
Oct 14, 2025
ivanov
approved these changes
Oct 14, 2025
minrk
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Back off plan to deprecate longstanding default paths. Folks can still opt-in to platformdirs, but there is little reason to change the defaults. Changing defaults is necessarily a long and sensitive process, and needs to come with documentation, support for migration, etc., none of which has happened in the long time since the proposed deprecation started.
Simpler approach: keep defaults, stop warning about them.
closes #309