Skip to content

Handling long paths [Windows]

Manuel edited this page Oct 20, 2015 · 1 revision

General

Sometimes it can be that the paths are too long during an migration. Windows has some problems with too long paths.

How do I know if I experience this problem

Most likely the script will crash under windows if you have too long paths in the method handle_captitalization_filename_changes when an os.chdir is performed.

The error will look like: FileNotFoundError: [WinError 206] The filename or extension is too long

What can I do to prevent this error?

Git has a (experimental) feature which helps to prevent such errors. You can enable it by enter following command on your console/git bash: git config --system core.longpaths true

Afterwards you can restart your migration and everything should work as usual.