# Build Failing Due to Python 3.8 / get-pip.py Incompatibility **URL:** \ **Category:** Build Environment\ **Created:** [April 28, 2025, 11:37pm UTC](https://discuss.circleci.com/t/build-failing-due-to-python-3-8-get-pip-py-incompatibility/53181 "2025-04-28T23:37:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![chamayati](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@chamayati](https://discuss.circleci.com/u/chamayati)\ **Post date:** [April 28, 2025, 11:37pm UTC](https://discuss.circleci.com/t/build-failing-due-to-python-3-8-get-pip-py-incompatibility/53181/1 "2025-04-28T23:37:29Z")
Hi CircleCI team, We’ve recently encountered a build failure related to Python 3.8 and get-pip.py, despite using the same Docker image and pipeline setup that has worked for other jobs in the past. Here’s the output we’re seeing: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2225k 100 2225k 0 0 20.1M 0 --:–:-- --:–:-- --:–:-- 20.3M ERROR: This script does not work on Python 3.8. The minimum supported Python version is 3.9. Please use [https://bootstrap.pypa.io/pip/3.8/get-pip.py](https://bootstrap.pypa.io/pip/3.8/get-pip.py) instead. Exited with code exit status 1 To clarify: - These are **different jobs** , not reruns of previously successful ones. - They **use the same Docker image** and pipeline setup as previous jobs that **succeeded a few weeks ago**. - We **don’t explicitly use Python** in our build process. - The issue appears to be triggered by some background attempt to fetch or run `get-pip.py`, which now fails under Python 3.8. Any idea what might be causing this now, and whether there’s a recommended workaround or fix? Thanks in advance for your help. ---
**Author:** ![vineet](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/vineet/32/36322_2.png) [@vineet](https://discuss.circleci.com/u/vineet)\ **Post date:** [April 29, 2025, 5:03am UTC](https://discuss.circleci.com/t/build-failing-due-to-python-3-8-get-pip-py-incompatibility/53181/2 "2025-04-29T05:03:16Z")
@chamayati I’m facing the exactly same issue. Found your thread, just here to leave a +1 Hopefully, someone from CircleCI will look into it. ---
**Author:** ![vineet](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/vineet/32/36322_2.png) [@vineet](https://discuss.circleci.com/u/vineet)\ **Post date:** [April 29, 2025, 5:25am UTC](https://discuss.circleci.com/t/build-failing-due-to-python-3-8-get-pip-py-incompatibility/53181/3 "2025-04-29T05:25:12Z")
> [@chamayati](#): > > Any idea what might be causing this now, and whether there’s a recommended workaround or fix? @chamayati Are you using `path-filtering` or `continuation` orbs? I upgraded the above orbs’ versions and the error went away! ---
**Author:** ![chamayati](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@chamayati](https://discuss.circleci.com/u/chamayati)\ **Post date:** [April 29, 2025, 6:41am UTC](https://discuss.circleci.com/t/build-failing-due-to-python-3-8-get-pip-py-incompatibility/53181/4 "2025-04-29T06:41:25Z")
I believe we are using path-filtering ---
**Author:** ![chamayati](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@chamayati](https://discuss.circleci.com/u/chamayati)\ **Post date:** [April 29, 2025, 7:09am UTC](https://discuss.circleci.com/t/build-failing-due-to-python-3-8-get-pip-py-incompatibility/53181/5 "2025-04-29T07:09:27Z")
@vineet Just upgraded the path-filtering orbs—works like a charm. Thanks! ---
**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\ **Post date:** [May 6, 2025, 7:10am UTC](https://discuss.circleci.com/t/build-failing-due-to-python-3-8-get-pip-py-incompatibility/53181/6 "2025-05-06T07:10:17Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.