# Python subprocess can't work more **URL:** \ **Category:** Environments\ **Tags:** python\ **Created:** [July 26, 2019, 12:46pm UTC](https://travis-ci.community/t/python-subprocess-cant-work-more/4403 "2019-07-26T12:46:31Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [July 26, 2019, 2:30pm UTC](https://travis-ci.community/t/python-subprocess-cant-work-more/4403/2 "2019-07-26T14:30:30Z")
> **[Xenial as the default build environment - Travis CI changelog](https://changelog.travis-ci.com/xenial-as-the-default-build-environment-99476)** > >  New   > As announced two weeks ago, we've started incrementally updating the default build environment to Ubuntu... In particular, in the raw log, I see an error about `pip` inable to upgrade some (presumably apt-installed) Python packages which ultimately results in an error about an incompatible version of one of them being present. > [@Python 3.6 and 3.7 with system\_site\_packages enabled fails to activate on xenial](https://travis-ci.community/t/python-3-6-and-3-7-with-system-site-packages-enabled-fails-to-activate-on-xenial/1697/2): > > You don’t. "System site-packages" is only a thing for Python versions provided by distro – which for Xenial are [2.7.12](https://packages.ubuntu.com/xenial-updates/python) and [3.5.1](https://packages.ubuntu.com/xenial/python3). Other Python versions are installed manually (into /opt as of this writing), and the only global packages there are pip and setuptools (you can see all this by examining the Python tarball that the build log refers to). So if you’re using alternative Python versions, you don’t have access to any apt-get Python packages anyway. As such, the most straightforward solu… --- _[View the full topic](https://travis-ci.community/t/python-subprocess-cant-work-more/4403)._