# Python support on Windows

**URL:** <https://travis-ci.community/t/python-support-on-windows/241>\
**Category:** Windows\
**Created:** [October 11, 2018, 2:20pm UTC](https://travis-ci.community/t/python-support-on-windows/241 "2018-10-11T14:20:49Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**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:** [April 2, 2019, 9:41am UTC](https://travis-ci.community/t/python-support-on-windows/241/18 "2019-04-02T09:41:38Z")

</div>

Why can’t the following intuitive approach work and be fast??

```
language: python
python: 3.7
os:
  - linux
  - osx
  - windows
install: pip3 install --upgrade pip
script: python3 platform-info.py

```

The [minimal .travis.yml](https://github.com/cclauss/Travis-CI-Python-on-three-OSes) file required to run Python 3.7 on Linux, macOS, and Windows is unnecessary complex, fragile, and slow. Would it at least be possible to have **choco install python** done on the Windows base image to save a 1 min 30 sec startup time?

[https://docs.travis-ci.com/user/languages/python/#running-python-tests-on-multiple-operating-systems](https://docs.travis-ci.com/user/languages/python/#running-python-tests-on-multiple-operating-systems)

> **[cclauss/Travis-CI-Python-on-three-OSes](https://github.com/cclauss/Travis-CI-Python-on-three-OSes)**
>
> Minimal .travis.yml file to run the current Python 3.7 on Linux, macOS, and Windows - cclauss/Travis-CI-Python-on-three-OSes

---

_[View the full topic](https://travis-ci.community/t/python-support-on-windows/241)._