Give ibm_db's Native Driver Downloader the Proxy Environment
An ibm_db source build can fetch clidriver with urllib after pip has already obtained the Python package.
If pip obtains ibm_db but the source installation fails while downloading clidriver, configure the build script's urllib request too. A pip-only proxy argument does not configure every child downloader.
Before launching the source installation from a POSIX shell:
export https_proxy=http://proxy.example.net:8080
export http_proxy=http://proxy.example.net:8080urllib's default proxy handler uses the variables for the corresponding destination schemes. Retain no_proxy exceptions consistent with reaching the driver host. When public driver downloads may use public intermediaries, the HTTP proxy list supplies candidates for these environment URLs.
Keep the failing URL from the build output. A clidriver download refusal precedes Db2 connection setup and is not repaired through a database connection string.
The extra download depends on installation path. Compatible wheels or a deliberately supplied native driver can change what is fetched. For a supported source build using an existing driver, IBM_DB_HOME names its installation directory with the required headers and libraries; an empty directory provides none of them.