Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: default install directory result in import error #807

Closed
yetong2023 opened this issue Mar 31, 2024 · 4 comments
Closed

Bug: default install directory result in import error #807

yetong2023 opened this issue Mar 31, 2024 · 4 comments

Comments

@yetong2023
Copy link

To reproduce this:
`
!pip install paddlepaddle
import paddle

WinError 123 The name of the file or directory name tag syntax is incorrect:'\\?\C:\Users\yt\AppData\Roaming\jupyterlab-desktop\jlab_server\Lib\site-packages\paddle\base\..\libs'`

While in other platform, such as anoconda jupyterlab, winpython jupyterlab, there is no such error.

@yetong2023 yetong2023 added the bug label Mar 31, 2024
Copy link

welcome bot commented Mar 31, 2024

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@JasonWeill
Copy link

@yetong2023 Thanks for opening this issue! Which version of JupyterLab Desktop are you using and which Windows version are you using?

@mbektas
Copy link
Member

mbektas commented Apr 7, 2024

I have been debugging this issue together with #784 and they both have the same root cause. When bundled environment is installed on Windows, the environment prefix has UNC path format, starting with \\?\. Python (or some libraries) are not able to resolve those paths, causing these errors.

@yetong2023 as a workaround you can create a new Python environment (using New environment option) and install the dependency there.

@JasonWeill
Copy link

@yetong2023 Any update regarding the most recent comment from @mbektas ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants