Cant install 3.0.4 on windows 11 and Python 3.9.7+

[ItamarShDev]

trying to build our JLab env in Windows 11 failed with the following error:

Failed to build jupyter-bokeh
ERROR: Could not build wheels for jupyter-bokeh which use PEP 517 and cannot be installed directly
WARNING: You are using pip version 21.1.2; however, version 22.0.3 is available.
You should consider upgrading via the 'C:\Users\ItamarSharify\Documents\modeling\MOD\Scripts\python.exe -m pip install --upgrade pip' command.

The same error happened on:

1. both old and latest pip
2. both old and latest setuptools
3. python 3.9.7 and python 3.9.9
4. 2 different windows PCs, one with Windows 11 and one with Windows 10

This is not happening in Ubuntu 20.04 machines.
We have one Windows 11 pc that for some reason manages to install it.

Reverting to 3.0.2 works.

Here is the full pp install log:
pip install.txt

[bryevdv]

No idea what might be going on, but you might try the suggestions here in the mean time:

https://stackoverflow.com/a/63999596/3406693

[bryevdv]

@philippjfr @mattpap do we not publish wheels? Is that intentional? I thought we did now but I only see sdist at https://pypi.org/project/jupyter-bokeh/#files

Edit: I will have to see if I can manually publish a wheel in the next few days, until #141 is worked on

[bryevdv]

@ItamarShDev there is now a wheel (just for 3.0.4)

dev-3.9 ❯ pip install jupyter_bokeh
Collecting jupyter_bokeh
  Downloading jupyter_bokeh-3.0.4-py3-none-any.whl (1.4 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.4/1.4 MB 12.8 MB/s eta 0:00:00

can you see if this now works for you? If so this issue can be closed since the other issue is still open about publishing wheels in general

@philippjfr @mattpap FYI I built the wheel from the downloaded sdist with bdist_wheel AFAIK that should work fine

[ItamarShDev]

Works! thank you very much @bryevdv !

[philippjfr]

Thanks @bryevdv! I've never actually had the time to get set up to build and upload any packages for this repo. At some point I would like to automate it with GH Actions like we have for HoloViz packages.

[ItamarShDev]

I would be happy to help if you could point me to the right direction :)

…

On Thu, Mar 3, 2022, 22:20 Philipp Rudiger ***@***.***> wrote: Thanks @bryevdv <https://github.com/bryevdv>! I've never actually had the time to get set up to build and upload any packages for this repo. At some point I would like to automate it with GH Actions like we have for HoloViz packages. — Reply to this email directly, view it on GitHub <#146 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHIYG467ZRI7SRSJGHQC7TU6ENIJANCNFSM5PWVWWKQ> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[jgbustos]

trying to build our JLab env in Windows 11 failed with the following error:

Failed to build jupyter-bokeh
ERROR: Could not build wheels for jupyter-bokeh which use PEP 517 and cannot be installed directly
WARNING: You are using pip version 21.1.2; however, version 22.0.3 is available.
You should consider upgrading via the 'C:\Users\ItamarSharify\Documents\modeling\MOD\Scripts\python.exe -m pip install --upgrade pip' command.

The same error happened on:

1. both old and latest pip

2. both old and latest setuptools

3. python 3.9.7 and python 3.9.9

4. 2 different windows PCs, one with Windows 11 and one with Windows 10

This is not happening in Ubuntu 20.04 machines. We have one Windows 11 pc that for some reason manages to install it.

Reverting to 3.0.2 works.

Here is the full pp install log: pip install.txt

I have exactly the same problem on my machine. The only way I can make it build is by forcing pip and setuptools into legacy behaviour, ignoring pyproject.toml and building based on setup.py.

Try running
pip install -U --use-deprecated=legacy-resolver jupyter-bokeh

[pinusm]

Another solution, as pointed out by @jgbustos, is to allow Windows to use longer paths and removing the max path limitation.

Your administrator will need to activate the “Enable Win32 long paths” group policy, or set LongPathsEnabled to 1 in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
...
After changing the above option, no further configuration is required.

See source here.