Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA. This is necessary for legal reasons before we can look at your contribution. Please follow these steps to help rectify the issue:

1. If you don't have an account on b.p.o, please create one
2. Make sure your GitHub username is listed in "Your Details" at b.p.o
3. If you have not already done so, please sign the PSF contributor agreement
4. If you just signed the CLA, please wait at least one US business day and then check "Your Details" on bugs.python.org to see if your account has been marked as having signed the CLA (the delay is due to a person having to manually check your signed CLA)
5. Reply here saying you have completed the above steps

Thanks again to your contribution and we look forward to looking at it!

Hey folks! I was wondering why my PR keeps failing, even though I did a rebase a couple of days ago! Can someone elucidate what might be going on here, please? From what I'm noticing, the Travis job has a different config than other jobs, so I'm kinda confused about why is that. Thanks a lot!

It's totally fine to just do a merge if that's easier since we will do a squash commit in the end. I've restarted the Travis job just in case it was a weird fluke, though.

Rebasing the branch on latest master does not fix it.
It seems to be that the travis build is not even run my latest commit, but on a random one de1d4fc .
On the other hand, the appveyor build seems fine.

Maybe try doing a merge instead of a rebase? We've had issues in the past of Travis only grabbing the last 50 commits so that can lead to issues with older PRs.

Thanks for the PR, @ioanatia.

• Travis build failed:

/home/travis/build/python/cpython/Doc/library/pyexpat.rst:872:Footnote [#] is not referenced.

The change seems unrelated to your change, but unless that got fixed we can't accept the PR.

I realize this PR is quite old, so it's possible the fix for the failed travis build has already been done.
Will it be possible to rebase it off the latest master branch? If it's easier feel free to open a new PR.

• Please add yourself to Misc/ACKs file (there's a brief info about that here

• Please add a news entry describing this change. It can be added using blurb add.

The instruction for blurb add is here
There are additional details about how to write the news entry here
blurb is available in python >= 3.5

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

thanks @Mariatta !
I rebased this branch on latest master multiple times, but somehow the Travis build seems to pick up the same unrelated commit de1d4fc .

Not sure what else I can do than to close this one and reopen it in #6917.