# Utilizing System Python for Library Installation in Superbuild Process

**URL:** https://discourse.paraview.org/t/utilizing-system-python-for-library-installation-in-superbuild-process/13491
**Category:** ParaView Support
**Created:** [December 12, 2023, 8:09pm UTC](https://discourse.paraview.org/t/utilizing-system-python-for-library-installation-in-superbuild-process/13491 "2023-12-12T20:09:51Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![HollowSun0](https://discourse.paraview.org/user_avatar/discourse.paraview.org/hollowsun0/32/431_2.png) [@HollowSun0](https://discourse.paraview.org/u/HollowSun0)
#### Post date: [December 12, 2023, 8:09pm UTC](https://discourse.paraview.org/t/utilizing-system-python-for-library-installation-in-superbuild-process/13491/1 "2023-12-12T20:09:51Z")

</div>

During the superbuild process, Python and the necessary packages are installed. However, within my Docker container, I wish to use my own Python. To achieve this, I typically set `USE_SYSTEM_python3=OFF`.

Subsequently, I’ve observed that none of the Python packages (such as ‘pathlib’) are installed, as my Python environment is a basic, unmodified (‘vanilla’) version.

Is there an efficient method to install the Python packages specified in the superbuild onto the system-provided Python?

Thank you 🙂

Patrick

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [December 15, 2023, 3:11pm UTC](https://discourse.paraview.org/t/utilizing-system-python-for-library-installation-in-superbuild-process/13491/2 "2023-12-15T15:11:10Z")

</div>

> [@HollowSun0](#):
>
> Subsequently, I’ve observed that none of the Python packages (such as ‘pathlib’) are installed, as my Python environment is a basic, unmodified (‘vanilla’) version.

`pathlib` is a stdlib thing, so it should have it…

> [@HollowSun0](#):
>
> During the superbuild process, Python and the necessary packages are installed. However, within my Docker container, I wish to use my own Python. To achieve this, I typically set `USE_SYSTEM_python3=OFF`.

Well, that tells the superbuild to build its own copy. If you want to use a Python install the superbuild doesn’t build itself, you want to turn `USE_SYSTEM_python3=ON`.

---

<div class="post-metadata">

### Author: ![HollowSun0](https://discourse.paraview.org/user_avatar/discourse.paraview.org/hollowsun0/32/431_2.png) [@HollowSun0](https://discourse.paraview.org/u/HollowSun0)
#### Post date: [January 3, 2024, 3:58pm UTC](https://discourse.paraview.org/t/utilizing-system-python-for-library-installation-in-superbuild-process/13491/3 "2024-01-03T15:58:55Z")

</div>

So that means there’s no easy way to have a hybrid? i.e.

1. Use system python
2. Install required packages during superbuild

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 3, 2024, 4:11pm UTC](https://discourse.paraview.org/t/utilizing-system-python-for-library-installation-in-superbuild-process/13491/4 "2024-01-03T16:11:44Z")

</div>

The superbuild should be able to install its packages to its own `install/` directory.
