# Trouble with Python build matrix being respected by jobs

**URL:** <https://travis-ci.community/t/trouble-with-python-build-matrix-being-respected-by-jobs/3432>\
**Category:** Uncategorized\
**Tags:** bug\
**Created:** [May 17, 2019, 3:14am UTC](https://travis-ci.community/t/trouble-with-python-build-matrix-being-respected-by-jobs/3432 "2019-05-17T03:14:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [May 17, 2019, 4:42am UTC](https://travis-ci.community/t/trouble-with-python-build-matrix-being-respected-by-jobs/3432/2 "2019-05-17T04:42:31Z")

</div>

`include:` jobs exist independently from the build matrix and are added on top of it.

So you get two jobs from the `python:` axis in the default `test` stage, accompanied with all the jobs you specified in `include:`, without a `python:` setting.

AFAICS from [https://docs.travis-ci.com/user/build-stages/#how-to-define-build-stages](https://docs.travis-ci.com/user/build-stages/#how-to-define-build-stages) , stages are not considered an axis so you cannot add jobs to more than one stage using the matrix.

As such, the way to go seems to be to either

- specify all the jobs manually, [using YAML aliases](https://docs.travis-ci.com/user/build-stages/using-yaml-aliases/) to reduce duplication, or
- only manually duplicate jobs as above in stages with fewer jobs and specify `python:` for them manually.

---

_[View the full topic](https://travis-ci.community/t/trouble-with-python-build-matrix-being-respected-by-jobs/3432)._