### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 11:11am UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/1 "2024-09-20T11:11:51Z")
I have been trying to install one package in slicer and I am facing the following issue
> Building wheels for collected packages: spatial\_correlation\_sampler
> Building wheel for spatial\_correlation\_sampler (pyproject.toml) … error
> error: subprocess-exited-with-error
> × Building wheel for spatial\_correlation\_sampler (pyproject.toml) did not run successfully.
> │ exit code: 1
> ╰─\> [19 lines of output]
> running bdist\_wheel
> C:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\lib\Python\Lib\site-packages\torch\utils\cpp\_extension.py:495: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja… Falling back to using the slow distutils backend.
> warnings.warn(msg.format(‘we could not find ninja.’))
> running build
> running build\_py
> creating build\lib.win-amd64-cpython-39\spatial\_correlation\_sampler
> copying Correlation\_Module\spatial\_correlation\_sampler\spatial\_correlation\_sampler.py → build\lib.win-amd64-cpython-39\spatial\_correlation\_sampler
> copying Correlation\_Module\spatial\_correlation\_sampler\__init_\_.py → build\lib.win-amd64-cpython-39\spatial\_correlation\_sampler
> running build\_ext
> C:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\lib\Python\Lib\site-packages\torch\utils\cpp\_extension.py:414: UserWarning: The detected CUDA version (12.6) has a minor version mismatch with the version that was used to compile PyTorch (12.1). Most likely this shouldn’t be a problem.
> warnings.warn(CUDA\_MISMATCH\_WARN.format(cuda\_str\_version, torch.version.cuda))
> building ‘spatial\_correlation\_sampler\_backend’ extension
> creating build\temp.win-amd64-cpython-39\Release\Correlation\_Module
> “C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.42.34321\bin\HostX86\x64\cl.exe” /c /nologo /O2 /W3 /GL /DNDEBUG /MD -DUSE\_CUDA “-IC:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\lib\Python\Lib\site-packages\torch\include” “-IC:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\lib\Python\Lib\site-packages\torch\include\torch\csrc\api\include” “-IC:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\lib\Python\Lib\site-packages\torch\include\TH” “-IC:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\lib\Python\Lib\site-packages\torch\include\THC” “-IC:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.6\include” “-IC:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\lib\Python\include” “-IC:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\lib\Python\Include” “-IC:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.42.34321\include” “-IC:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.42.34321\ATLMFC\include” “-IC:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Auxiliary\VS\include” “-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt” “-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\um” “-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\shared” “-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\winrt” “-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\cppwinrt” “-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um” /EHsc /TpCorrelation\_Module\correlation.cpp /Fobuild\temp.win-amd64-cpython-39\Release\Correlation\_Module\correlation.obj /MD /wd4819 /wd4251 /wd4244 /wd4267 /wd4275 /wd4018 /wd4190 /wd4624 /wd4067 /wd4068 /EHsc -std=c++17 -fopenmp -DTORCH\_API\_INCLUDE\_EXTENSION\_H -DTORCH\_EXTENSION\_NAME=spatial\_correlation\_sampler\_backend -D\_GLIBCXX\_USE\_CXX11\_ABI=0 /std:c++17
> cl : Command line warning D9002 : ignoring unknown option ‘-std=c++17’
> cl : Command line warning D9002 : ignoring unknown option ‘-fopenmp’
> correlation.cpp
> C:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\lib\Python\Lib\site-packages\torch\include\torch/csrc/python\_headers.h(12): fatal error C1083: Cannot open include file: ‘Python.h’: No such file or directory
> error: command ‘C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.42.34321\bin\HostX86\x64\cl.exe’ failed with exit code 2
> [end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for spatial\_correlation\_sampler
Failed to build spatial\_correlation\_sampler
ERROR: Could not build wheels for spatial\_correlation\_sampler, which is required to install pyproject.toml-based projects
[notice] A new release of pip is available: 23.0 → 24.2
[notice] To update, run: python-real.exe -m pip install --upgrade pip
PS C:\Users\TestProfile\AppData\Local\NA-MIC\Slicer 5.2.2\bin\> PythonSlicer.exe -m pip install python-dev
ERROR: Could not find a version that satisfies the requirement python-dev (from versions: none)
ERROR: No matching distribution found for python-dev
[notice] A new release of pip is available: 23.0 → 24.2
---
### Author:  [@cpinter](https://discourse.slicer.org/u/cpinter)
#### Post date: [September 20, 2024, 11:14am UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/2 "2024-09-20T11:14:00Z")
Does this happen on the latest stable 5.6.2? If yes, how about the latest preview?
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 11:16am UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/3 "2024-09-20T11:16:42Z")
Hi @cpinter I am using the Slicer 5.2.2 version, as one of the application/plugin developed supports only that specific version
package name : spatial\_correlation\_sampler
is there a solution for this
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 11:36am UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/4 "2024-09-20T11:36:51Z")
Is there a way to install python-dev as when I am looking for a solution for this issue, I am getting suggestion like this
---
### Author:  [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [September 20, 2024, 12:11pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/5 "2024-09-20T12:11:24Z")
Read the following linked post about methods of installing packages where Whl files are having to be built from source. To summarize, build the Whl in a system install of Python and use the cached Whl file to install in the Slicer Python. A Python package requiring build from source with no Whl files available from PyPI is generally an indication of a Python project with not a lot of support.
>
>
> Adding Python header and lib would make things worse for end users:
> \- Bad: User…s need to install build tools. Instead, if we included pre-built wheels in the extension package (the factory machine can do this) then users would not be forced to install anything else than Slicer.
> \- Bad: Developers would not realize that they are using a Python package that does not have wheels and so the extension would simply not work for users (it would only work on developer computers, where build tools are installed).
>
> For developers, it would be a mixed bag:
> \- Good: developers could more easily install packages without wheels. But a developer can build wheel by a workaround: install Python-3.9 and build tools on the computer and then pip install the package; next time when calling pip\_install in Slicer, the built wheel is found in the package cache and Slicer installs it (at least on Windows).
> \- Bad: Developers would not realize that they are considering relying on a low-quality Python package, which would be bad.
>
> There may be differences between platforms. For example, on Linux it is probably much more common to have developer tools installed, most end users are developers, providing compatible wheels is hard, and building components is part of normal life. However, in non-mainstream Linux environments entire Slicer may need to be built from source (and then it does not matter what the Slicer package includes).
>
> Adding the two files on a single platform sounds easy, but implementation on all platforms, adding tests, and assisting end users and extension developers with Python package build errors (what developer tools to install, how to configure, investigate build errors) could be significant one-time and continuous effort.
>
> Taking everything into consideration, I would lean towards not supporting building Python wheels in an installed Slicer, as the costs and disadvantages seem to outweigh the benefits.
---
### Author:  [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [September 20, 2024, 12:15pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/6 "2024-09-20T12:15:10Z")
> [@maniron](#):
>
> I am using the Slicer 5.2.2 version, as one of the application/plugin developed supports only that specific version
Which code is it? Slicer developers don’t support older versions of Slicer, but can help provide guidance on the latest stable and preview releases of Slicer.
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 12:15pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/7 "2024-09-20T12:15:15Z")
Hi @jamesobutler thanks for responding, I was able to install the same package locally, now how can I do the way you mentioned
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 12:16pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/8 "2024-09-20T12:16:02Z")
I mean the application which was developed by us in using slicer 5.2.2
---
### Author:  [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [September 20, 2024, 12:16pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/9 "2024-09-20T12:16:04Z")
For the sake of this thread and for others that might run into the problem, can you describe how you got it to install succesfully?
---
### Author:  [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [September 20, 2024, 12:16pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/10 "2024-09-20T12:16:58Z")
How can we get you to use latest Slicer stable and preview version? Slicer 5.2.2 is quite old. Are there compatibility issues with latest Slicer? Slicer developers can help with that.
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 12:18pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/11 "2024-09-20T12:18:29Z")
I installed that package using pip
> pip install spatial\_correlation\_sampler
before installing it I wanted to install torch
so used the below command to install the required torch and later I installed the package it got installed
> pip install torch torchvision torchaudio --index-url [https://download.pytorch.org/whl/cu121](https://download.pytorch.org/whl/cu121)
I am trying the same thing with SlicerPython.exe , but no luck
> PythonSlicer.exe -m pip install --trusted-host=[pytorch.org](http://pytorch.org) --trusted-host=[download.pytorch.org](http://download.pytorch.org) --trusted-host=[files.pytorch.org](http://files.pytorch.org) torch torchvision torchaudio --index-url [https://download.pytorch.org/whl/cu121](https://download.pytorch.org/whl/cu121)
above is the command I used to install torch
> PythonSlicer.exe -m pip install spatial\_correlation\_sampler
above command I used to install the package
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 12:19pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/12 "2024-09-20T12:19:19Z")
Is there a way where we can upgrade the python version in slicer, cause in my machine I have python 3.11 and slicer 5.2.2 is having 3.9.10
---
### Author:  [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)
#### Post date: [September 20, 2024, 12:20pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/13 "2024-09-20T12:20:31Z")
Updating Slicer’s Python version is a good bit of work that has not yet been completed by the Slicer developers, but the work is tracked at:
>
>
> \## Is your feature request related to a problem? Please describe.
>
> As I learne…d while working on #7046, the latest versions of python packages such as \`numpy\` and \`scipy\` now have a python minimum of 3.9 which is the version currently used by Slicer (3.9.10). Per \[NEP29 drop schedule\](https://numpy.org/neps/nep-0029-deprecation\_policy.html#drop-schedule), Python 3.9 support will begin to be dropped by major python packages beginning April 5th, 2024. However, NEP29 has now been superseded by \[SPEC 0\](https://scientific-python.org/specs/spec-0000/) where the \[drop schedule\](https://scientific-python.org/specs/spec-0000/#drop-schedule) states to drop Python 3.9 support in new releases starting in 2023 Q4 (marking the end of 3 years of support). Writing up this issue is to stay ahead of the deprecation curve so that Slicer does not get into a situation of not being able to use the latest versions of major python packages.
>
> \## To answer the question: Is the newer version of Python supported by the open source community?
> When Slicer was updated from 3.6.7 to 3.9.10 in https://github.com/Slicer/Slicer/commit/34e48e8aef5dad19ec8a955d6f48a1940846e3f3:
> It was January 25th, 2022 and the "\[python readiness\](https://pyreadiness.org/)" for Python 3.9 was that \[64.7%\](https://github.com/di/pyreadiness/blob/50d28f9bcf62edf5f42e237082f1a3c93f8be3e1/docs/3.9/index.html#L69) of the most popular python packages had explicit support for 3.9 as stated on pypi.org.
>
> |Date | Python 3.9 | Python 3.10 | Python 3.11 | Python 3.12|
> |------|-------------|--------------|---------------|--------------|
> |June 28th, 2023|\[78.6%\](https://github.com/di/pyreadiness/blob/a7f95961c5615d5eb336ad646fe3d1aae8cf8c55/docs/3.9/index.html#L95)|\[72.8%\](https://github.com/di/pyreadiness/blob/a7f95961c5615d5eb336ad646fe3d1aae8cf8c55/docs/3.10/index.html#L95)|\[51.7%\](https://github.com/di/pyreadiness/blob/a7f95961c5615d5eb336ad646fe3d1aae8cf8c55/docs/3.11/index.html#L95)||
> |August 24th, 2023|\[80.8%\](https://github.com/di/pyreadiness/blob/949c860148e24c6976ff8de76435e663e610d2da/docs/3.9/index.html#L95)|\[76.4%\](https://github.com/di/pyreadiness/blob/949c860148e24c6976ff8de76435e663e610d2da/docs/3.10/index.html#L95)|\[60.6%\](https://github.com/di/pyreadiness/blob/949c860148e24c6976ff8de76435e663e610d2da/docs/3.11/index.html#L95)||
> |October 28th, 2023|\[80.0%\](https://github.com/di/pyreadiness/blob/bad9df0eafc04ebf06bbd01ff97be2235a96e841/docs/3.9/index.html#L95)|\[76.1%\](https://github.com/di/pyreadiness/blob/bad9df0eafc04ebf06bbd01ff97be2235a96e841/docs/3.10/index.html#L95)|\[64.4%\](https://github.com/di/pyreadiness/blob/bad9df0eafc04ebf06bbd01ff97be2235a96e841/docs/3.11/index.html#L95)||
> |December 20th, 2023|\[80.8%\](https://github.com/di/pyreadiness/blob/b8ab80f82fcc088aa44b3ad9ed26151c70f301cb/docs/3.9/index.html#L95)|\[76.9%\](https://github.com/di/pyreadiness/blob/b8ab80f82fcc088aa44b3ad9ed26151c70f301cb/docs/3.10/index.html#L95)|\[67.5%\](https://github.com/di/pyreadiness/blob/b8ab80f82fcc088aa44b3ad9ed26151c70f301cb/docs/3.11/index.html#L95)||
> |March 4th, 2024|\[82.8%\](https://github.com/di/pyreadiness/blob/764e4520b314c28658f099299b3c7670280ffeb5/docs/3.9/index.html#L95)|\[78.9%\](https://github.com/di/pyreadiness/blob/764e4520b314c28658f099299b3c7670280ffeb5/docs/3.10/index.html#L95)|\[69.7%\](https://github.com/di/pyreadiness/blob/764e4520b314c28658f099299b3c7670280ffeb5/docs/3.11/index.html#L95)|\[48.6%\](https://github.com/di/pyreadiness/blob/764e4520b314c28658f099299b3c7670280ffeb5/docs/3.12/index.html#L95)|
> |May 17th, 2024|\[80.8%\](https://github.com/di/pyreadiness/blob/bfe7422e412f0305b6762dcefa4849a8bb05384e/docs/3.9/index.html#L95)|\[77.5%\](https://github.com/di/pyreadiness/blob/bfe7422e412f0305b6762dcefa4849a8bb05384e/docs/3.10/index.html#L95)|\[71.1%\](https://github.com/di/pyreadiness/blob/bfe7422e412f0305b6762dcefa4849a8bb05384e/docs/3.11/index.html#L95)|\[55.0%\](https://github.com/di/pyreadiness/blob/bfe7422e412f0305b6762dcefa4849a8bb05384e/docs/3.12/index.html#L95)|
> |August 14th, 2024|\[82.8%\](https://github.com/di/pyreadiness/blob/a3467a9865e6326f2accb218c43ea9a187a8e39a/docs/3.9/index.html#L95)|\[80.8%\](https://github.com/di/pyreadiness/blob/a3467a9865e6326f2accb218c43ea9a187a8e39a/docs/3.10/index.html#L95)|\[74.7%\](https://github.com/di/pyreadiness/blob/a3467a9865e6326f2accb218c43ea9a187a8e39a/docs/3.11/index.html#L95)|\[62.2%\](https://github.com/di/pyreadiness/blob/a3467a9865e6326f2accb218c43ea9a187a8e39a/docs/3.12/index.html#L95)|
>
> \## Describe the solution you'd like
>
> \- Update Slicer's Python from 3.9 to 3.10.
>
> Based on Slicer's previous update to Python 3.9 at 64.7% readiness and Python 3.10 at a higher readiness than that, this means Slicer can consider Python 3.10 ready to update to pending Python 3.10 support at:
> \- https://github.com/python-cmake-buildsystem/python-cmake-buildsystem
> \- https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/pull/281
>
> \## Describe alternatives you've considered
>
> \- Update Slicer's Python from 3.9 to 3.12. This should be considered especially if the python-readiness for Python 3.12 (https://pyreadiness.org/3.12/) has increased when a developer begins to execute on this update.
Slicer 5.2.2 will definitely not ever be updated to support a newer python version.
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 12:21pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/14 "2024-09-20T12:21:44Z")
Hmm got it but atleast if I could be able to install this package it would be more helpful
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 12:23pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/15 "2024-09-20T12:23:05Z")
> [@maniron](#):
>
> fatal error C1083: Cannot open include file: ‘Python.h’: No such file or directory
For this error I placed all the required header files in the python include folder , now this error is not coming but I am getting the link error
LINK : warning LNK4044: unrecognized option ‘/lgomp’; ignored
LINK : fatal error LNK1104: cannot open file ‘python39.lib’
error: command ‘C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.42.34321\bin\HostX86\x64\link.exe’ failed with exit code 1104
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 20, 2024, 12:25pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/16 "2024-09-20T12:25:37Z")
Can you help me with this, so that I will try this way and see whether I have a solution for the issue
---
### Author:  [@muratmaga](https://discourse.slicer.org/u/muratmaga)
#### Post date: [September 20, 2024, 4:06pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/17 "2024-09-20T16:06:25Z")
Others might chime in but i think you will have to build both Slicer and this python package from source using the same build tools to avoid that problem.
I thought things worked in ubuntu, maybe focus on working on that?
---
### Author:  [@muratmaga](https://discourse.slicer.org/u/muratmaga)
#### Post date: [September 20, 2024, 4:21pm UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/18 "2024-09-20T16:21:25Z")
Also, why are you trying with 5.2.2? Did you try with the latest stable?
---
### Author:  [@maniron](https://discourse.slicer.org/u/maniron)
#### Post date: [September 23, 2024, 5:38am UTC](https://discourse.slicer.org/t/facing-issue-while-installing-python-package/38459/19 "2024-09-23T05:38:21Z")
I am actually consuming one of the plugin which is developed with this version of Slicer and making changes to it . Thats the main reason I using this version. Tried with latest version of slicer but the plugin is not working