# Python 3.9.0 build **URL:** \ **Category:** Python\ **Created:** [October 5, 2020, 5:56pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091 "2020-10-05T17:56:56Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![RhinosF1](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/rhinosf1/32/5270_2.png) [@RhinosF1](https://travis-ci.community/u/RhinosF1)\ **Post date:** [October 5, 2020, 5:56pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/1 "2020-10-05T17:56:56Z")
Hi, Python 3.9.0 came out today so I restarted the job [https://travis-ci.com/github/MirahezeBots/MirahezeBots/jobs/394787945](https://travis-ci.com/github/MirahezeBots/MirahezeBots/jobs/394787945) but it still gives a 404 and fails. My alias is set to 3.9 Can someone point out if I’m missing something obvious or help get it working? Thanks! ---
**Author:** ![mgedmin](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/mgedmin/32/464_2.png) [@mgedmin](https://travis-ci.community/u/mgedmin)\ **Post date:** [October 5, 2020, 6:45pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/2 "2020-10-05T18:45:53Z")
AFAIU 3.9.0 final is [not yet available](https://docs.travis-ci.com/user/languages/python/#python-versions) on Travis CI, but you can use 3.9-dev. I’m not entirely certain how Travis adds support for Python versions. From past discussions I seem to remember that pyenv has to support 3.9 first, which appears to [already have happened](https://github.com/pyenv/pyenv/pull/1706), so now what I think we need is a PR for [https://github.com/travis-ci/cpython-builder/](https://github.com/travis-ci/cpython-builder/)? If I understood the project structure, I’d try to create one… UPDATE: ok, it seems to me no PR is necessary, just someone from Travis ([last time](https://travis-ci.community/t/add-python-3-8-support/5463/5) it was @BanzaiMan) has to trigger a manual build with VERSION=3.9.0. ---
**Author:** ![RhinosF1](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/rhinosf1/32/5270_2.png) [@RhinosF1](https://travis-ci.community/u/RhinosF1)\ **Post date:** [October 5, 2020, 6:57pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/3 "2020-10-05T18:57:26Z")
3.9-dev is currently added for us, I know they’re won’t be much difference. Thanks for the quick reply, hopefully we can get the build for 3.9 added soon. ---
**Author:** ![hugovk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hugovk/32/684_2.png) [@hugovk](https://travis-ci.community/u/hugovk)\ **Post date:** [October 5, 2020, 9:08pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/4 "2020-10-05T21:08:27Z")
> [@mgedmin](#): > > From past discussions I seem to remember that pyenv has to support 3.9 first, which appears to [already have happened](https://github.com/pyenv/pyenv/pull/1706), so now what I think we need is a PR for [https://github.com/travis-ci/cpython-builder/](https://github.com/travis-ci/cpython-builder/)? Pyenv needs a release too? ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [October 5, 2020, 10:13pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/5 "2020-10-05T22:13:09Z")
> [@hugovk](#): > > Pyenv needs a release too? [No.](https://github.com/travis-ci/cpython-builder/blob/8a92b058f908e6be6c83cc653375ca372b9a462c/.travis.yml#L16-L17) ---
**Author:** ![marvin-w](https://avatars.discourse-cdn.com/v4/letter/m/a5b964/32.png) [@marvin-w](https://travis-ci.community/u/marvin-w)\ **Post date:** [October 9, 2020, 1:05pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/6 "2020-10-09T13:05:26Z")
PyEnv just released [v1.2.21](https://github.com/pyenv/pyenv/releases/tag/v1.2.21) ([Changelog](https://github.com/pyenv/pyenv/commit/806b30d6ce5b263a765648fbcdd68266833b7289)) which added support for python 3.9 ---
**Author:** ![cclauss](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/cclauss/32/912_2.png) [@cclauss](https://travis-ci.community/u/cclauss)\ **Post date:** [October 15, 2020, 6:20am UTC](https://travis-ci.community/t/python-3-9-0-build/10091/7 "2020-10-15T06:20:42Z")
What is the status here? Is there an open PR somewhere for us to review? Travis CI seems PSF, GithubActions, Homebrew, Pyenv all seem to be upgraded to support Py39 but Travis seems to be lagging… ---
**Author:** ![hughesp8](https://avatars.discourse-cdn.com/v4/letter/h/d26b3c/32.png) [@hughesp8](https://travis-ci.community/u/hughesp8)\ **Post date:** [October 15, 2020, 10:16am UTC](https://travis-ci.community/t/python-3-9-0-build/10091/8 "2020-10-15T10:16:03Z")
I would also appreciate Python 3.9 being available for my builds 🙂 ---
**Author:** ![bertonha](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/bertonha/32/5280_2.png) [@bertonha](https://travis-ci.community/u/bertonha)\ **Post date:** [October 7, 2020, 4:06pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/9 "2020-10-07T16:06:59Z")
Python 3.9 just got released last monday and Currently TravisCI 3.9 is getting a 404 ---
**Author:** ![pavdmyt](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/pavdmyt/32/5338_2.png) [@pavdmyt](https://travis-ci.community/u/pavdmyt)\ **Post date:** [October 17, 2020, 8:38am UTC](https://travis-ci.community/t/python-3-9-0-build/10091/10 "2020-10-17T08:38:05Z")
Having the same issue, Python 3.9 was released on October 5th, 2020, but still trying `3.9` gives 404. Only `3.9-dev` is available. Link to the build: [https://travis-ci.org/github/pavdmyt/yaspin/jobs/735624449](https://travis-ci.org/github/pavdmyt/yaspin/jobs/735624449) ---
**Author:** ![mikmatko](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/mikmatko/32/5352_2.png) [@mikmatko](https://travis-ci.community/u/mikmatko)\ **Post date:** [October 19, 2020, 2:34pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/11 "2020-10-19T14:34:49Z")
As mentioned earlier, it looks like this requires someone to trigger a manual build with VERSION=3.9.0 in [https://github.com/travis-ci/cpython-builder/](https://github.com/travis-ci/cpython-builder/) Pinging @BanzaiMan for the needful. Thanks! ---
**Author:** ![cclauss](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/cclauss/32/912_2.png) [@cclauss](https://travis-ci.community/u/cclauss)\ **Post date:** [October 25, 2020, 7:35pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/12 "2020-10-25T19:35:17Z")
Tap, tap, tap… What is the roadblock on this? ---
**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\ **Post date:** [October 26, 2020, 2:21pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/13 "2020-10-26T14:21:23Z")
Sorry for the delay. > **[Travis CI - Test and Deploy with Confidence](https://travis-ci.com/github/travis-ci/travis-nightly-builder/jobs/407408153)** > **[Travis CI - Test and Deploy with Confidence](https://travis-ci.com/github/travis-ci/cpython-builder/builds/192795784)** They should become available for use in the near future (up to 24 hours or so). ---
**Author:** ![hugovk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hugovk/32/684_2.png) [@hugovk](https://travis-ci.community/u/hugovk)\ **Post date:** [October 26, 2020, 7:47pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/14 "2020-10-26T19:47:11Z")
Thank you! The `xenial-arm64` build failed at [https://travis-ci.com/github/travis-ci/cpython-builder/builds/192795784](https://travis-ci.com/github/travis-ci/cpython-builder/builds/192795784), does it need a restart? ---
**Author:** ![RhinosF1](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/rhinosf1/32/5270_2.png) [@RhinosF1](https://travis-ci.community/u/RhinosF1)\ **Post date:** [October 26, 2020, 7:58pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/15 "2020-10-26T19:58:13Z")
Working for me on focal-graviton2, Thanks! ---
**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\ **Post date:** [October 26, 2020, 8:03pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/16 "2020-10-26T20:03:51Z")
That’s a compilation error with numpy. I don’t think a restart will fix the problem. ---
**Author:** ![hugovk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hugovk/32/684_2.png) [@hugovk](https://travis-ci.community/u/hugovk)\ **Post date:** [October 26, 2020, 8:07pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/17 "2020-10-26T20:07:25Z")
Yeah, probably not, they’re (kind of appropriately) waiting for their CI provider to add support for Python 3.9 (due tomorrow) so they can release wheels. Anyway, also confirmed 3.9 is now available for Xenial/Bionic/Focal, thanks again! ---
**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\ **Post date:** [October 26, 2020, 8:15pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/18 "2020-10-26T20:15:14Z")
Oh, that’s a pickle. I suppose I could do a one-off build of a 3.9 archive on this arch without numpy, so that numpy team can run builds? Would that work? Do you have a URL for their issue tracker? ---
**Author:** ![hugovk](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hugovk/32/684_2.png) [@hugovk](https://travis-ci.community/u/hugovk)\ **Post date:** [October 26, 2020, 8:18pm UTC](https://travis-ci.community/t/python-3-9-0-build/10091/19 "2020-10-26T20:18:42Z")
It’s okay, NumPy are waiting to do Windows wheels on Azure Pipelines, so we’re good here. Sorry for the confusion! > > > Hello. Could you please release CPython 3.9 manylinux wheels on PyPI? > Python 3.9.0 final was released this week: https://www.python.org/downloads/release/python-390/ > Thank You. ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [October 27, 2020, 12:11am UTC](https://travis-ci.community/t/python-3-9-0-build/10091/20 "2020-10-27T00:11:26Z")
> [@hugovk](#): > > Yeah, probably not, they’re (kind of appropriately) waiting for their CI provider to add support for Python 3.9 (due tomorrow) so they can release wheels. This Catch-22 situation is exactly why Travis stopped bundling extra modules with _nightly_ builds of Python. Any compilation problems, project maintainers should resolve there before the release. [Next page](https://travis-ci.community/t/python-3-9-0-build/10091.md?page=2)