uv fails to install `jupyter_contrib_nbextensions==0.7.0` while pip succeeds

[leodevian]

Hello,

I'm using uv 0.4.30 (61ed2a2 2024-11-04) on Windows and I'm trying to install jupyter_contrib_nbextensions==0.7.0. It seems that uv fails to install the package as it cannot be built with the latest versions of setuptools, due to some deprecations.

uv pip install jupyter_contrib_nbextensions==0.7.0

However, the latest version of pip (24.3.1) succeeds to build and install the package and I would like to understand this difference in behavior.

pip install jupyter_contrib_nbextensions==0.7.0

I read the documentation on build failures and I don't understand if I can force a version of setuptools and wheel for jupyter_contrib_nbextensions.

Also, can I manage this package with uv if it has been installed using pip?

Thank you for your awesome work!

[FishAlchemist]

I'm a Windows user and I couldn't reproduce the problem you mentioned.
Furthermore, according to your description, the package installed with uv is not the same as the one installed with pip. (Corrected)

[FishAlchemist]

@leodevian
I suggest you provide more complete information. After all, if we can't reproduce the issue, we won't know what the error message is. As for the method, at least add --verbose to get complete information.

[leodevian]

Thanks for your quick feedback! Indeed, I did mispell the package name in the description (now edited).

The following command should reproduce the issue:

mkdir issue
cd issue
uv venv -p 3.11 *> log.txt
uv pip install jupyter_contrib_nbextensions==0.7.0 -vvv *>> log.txt

I'm using cpython-3.11.10-windows-x86_64-none, which has been installed using uv.

Here are the logs with --verbose (I'm not used to redirection and struggled to get them).

log.txt

[FishAlchemist]

@leodevian Could you provide the pyproject.toml that can reproduce this issue? Because when I tried your problem, I used a default pyproject.toml.

Edit:
But it has a lot of warnings.

[leodevian]

@FishAlchemist I don't have pyproject.toml in my directory.

I tried the following commands and it still failed with the same error:

mkdir issue
cd issue
uv init -p 3.11
uv add jupyter_contrib_nbextensions==0.7.0

It seems that pip succeeds to build a wheel while uv fails?

EDIT: I don't understand the difference in behavior. Does pip support deprecated methods that have not been implemented in uv?

[charliermarsh]

Are you perhaps hitting the filename length limit on Windows?

[leodevian]

The directory is located in %USERPROFILE%, which is 18 characters long, so I doubt it.

I will try to reproduce the issue on my personal computer later, to investigate further.

[FishAlchemist]

Are you perhaps hitting the filename length limit on Windows?

It seems possible, as my computer enable Long Paths.

To check if it's enabled, you can simply open PowerShell to query. Reading the registry doesn't require administrative privileges.

Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" `
∙ -Name "LongPathsEnabled"

[charliermarsh]

Yes but the error you shared is for build\lib\jupyter_contrib_nbextensions\nbextensions\code_prettify\README_code_prettify.md which will already be nested inside the build cache directory.

[leodevian]

I don't have it and I have no admin rights on this computer. I will give your more information once I tried to reproduce the issue on my personal computer (with admin rights).

Could it be that building universal wheels is not supported by uv? To me, it seems that this feature has been deprecated for quite some time...

From the logs:

With Python 2.7 end-of-life, support for building universal wheels
        (i.e., wheels that support both Python 2 and Python 3)
        is being obviated.

[FishAlchemist]

Yes but the error you shared is for build\lib\jupyter_contrib_nbextensions\nbextensions\code_prettify\README_code_prettify.md which will already be nested inside the build cache directory.

@charliermarsh Yes, I just closed the long path, and then the problem occurred

Edit:
Can UV detect long paths that are not enabled during the build phase?

---

@leodevian This is the configuration method provided by Microsoft.
https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell#registry-setting-to-enable-long-paths

[leodevian]

@FishAlchemist Thanks a lot! I guess that's good news.

It pains me because I'm promoting uv within my organization and no one will be able to disable the maximum file path limitation because of internal policies...