windows long file path (>260 characters) error#195
Merged
AlexEMG merged 2 commits intoDeepLabCut:masterfrom Feb 1, 2019
Merged
windows long file path (>260 characters) error#195AlexEMG merged 2 commits intoDeepLabCut:masterfrom
AlexEMG merged 2 commits intoDeepLabCut:masterfrom
Conversation
n-poulsen
pushed a commit
that referenced
this pull request
Jun 14, 2024
popscallion
pushed a commit
to popscallion/DeepLabCut
that referenced
this pull request
Jan 21, 2026
windows long file path (>260 characters) error
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
2 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.
Error thrown on windows if the file path to an image is > 260 characters, can be fixed by adding the prefix: '\?' to the file path (https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file#maximum-path-length-limitation)