OSError(22, '无效参数') - 无法打开任何 `.ipynb` 和 `.py` 文件

我无法打开我过去拥有的任何 Jupyernotebook 或 python 文件，并且收到此错误：

Unreadable Notebook: C:\Users\[mypath]\main\main.ipynb OSError(22, 'Invalid argument')

[mypath] 是我从上面删除的目录的一部分。

我尝试通过 解决方案这篇文章 ，但仍然有同样的问题。

这也是我打开 .py 文件

Error! Traceback (most recent call last):
File "C:\Users\moham\anaconda3\lib\site-packages\tornado\web.py", line 1704, in _execute
result = await result
File "C:\Users\moham\anaconda3\lib\site-packages\tornado\gen.py", line 234, in wrapper
yielded = ctx_run(next, result)
File "C:\Users\moham\anaconda3\lib\site-packages\notebook\services\contents\handlers.py", line 111, in get
model = yield maybe_future(self.contents_manager.get(
File "C:\Users\moham\anaconda3\lib\site-packages\notebook\services\contents\filemanager.py", line 444, in get
model = self._file_model(path, content=content, format=format)
File "C:\Users\moham\anaconda3\lib\site-packages\notebook\services\contents\filemanager.py", line 371, in
_file_model
content, format = self._read_file(os_path, format)
File "C:\Users\moham\anaconda3\lib\site-packages\notebook\services\contents\fileio.py", line 306, in
_read_file
bcontent = f.read()
OSError: [Errno 22] Invalid argument

通过jupyterlab打开文件时遇到的错误。

The error message "OSError(22, 'Invalid argument')" usually indicates an issue with the filename or path you're trying to access, especially if it's happening with both .ipynb and .py files.

Here's a breakdown of common causes and solutions:

1. Special Characters in File or Directory Names:

• Issue: File or directory names containing invalid characters (like ? , * , : , < , > , | , \ ) can confuse the file system.
• Solution: Rename any files or directories within the path that contain these characters. Replace them with underscores or other allowed symbols.

2. File Path Length Limitations:

• Issue: Windows has a maximum path length limit (around 260 characters). Exceeding this can cause errors.
• Solution:
  • Shorten the Path: Try moving your project to a directory with a shorter path (e.g., C:\Projects\your_project ).
  • Enable Long Path Support (Windows 10+):
    1. Open "Local Group Policy Editor" (gpedit.msc).
    2. Navigate to "Computer Configuration" -> "Administrative Templates" -> "System" -> "Filesystem".
    3. Enable the "Enable Win32 long paths" policy.
    4. Restart your computer.

3. File Permissions:

• Issue: If you don't have the necessary read permissions on the files or directories, you might encounter this error.
• Solution:
  1. Right-click on the affected folder containing your files.
  2. Select "Properties" -> "Security" tab.
  3. Check if your username has "Read" permission. If not, click "Edit" and grant the appropriate permissions.

4. Corrupted Jupyter Notebook or Python Files:

• Issue: The files themselves could be corrupted.
• Solution:
  • Try opening with a text editor: If possible, open the .ipynb file in a plain text editor to see if there are any obvious issues with the JSON structure.
  • Create a new file: If you can open other notebooks but not specific ones, try creating a new notebook and copying the code (if possible) from the problematic one.

5. Issues with Jupyter Notebook Installation:

• Issue: A corrupted or misconfigured Jupyter installation can lead to problems.
• Solution:
  • Reinstall Jupyter Notebook: Try uninstalling and then reinstalling Jupyter Notebook: bash pip uninstall jupyter notebook pip install jupyter notebook

Additional Tips:

• Restart: Sometimes a simple restart of your computer can resolve temporary glitches.
• Run as Administrator: Try running Jupyter Notebook or your Python scripts as administrator to rule out any permission issues.

If none of these solutions work, please provide the following information for further assistance:

• Operating System: (e.g., Windows 10, macOS, Linux)
• Jupyter Notebook Version: (run jupyter --version in your terminal/command prompt)
• Python Version: (run python --version in your terminal/command prompt)
• Exact filename and path: (share the full path of one of the files you're trying to open)