Skip to content
This repository has been archived by the owner on Apr 14, 2022. It is now read-only.

Bump requirements versions #23

Merged
merged 4 commits into from
Mar 24, 2018

Conversation

pquentin
Copy link
Member

The exception is tornado which is still pinned at 4.x.

Maybe we should use ~= to pin to major versions?

We still use tornado 4.5, because the API of tornado 5.0 has
significantly changed.
`pytest` alone is deprecated.
pytest-timeout==1.2.0
pytest==3.4.0
gcp-devrel-py-tools==0.0.7
pytest-random-order==0.6.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I originally added this to help track down the weird timeout bug we were hitting on Windows, and then forgot to remove it. But maybe it's useful to keep -- what do you think?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do like it! It can be surprising/annoying at times, but I've seen enough tests depending on each other to know that it can help detect annoying issues earlier.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

However it seems to break --failed-first, which is possibly more useful.

pytest-random-order==0.6.0
pytest-timeout==1.2.1
pytest==3.4.2
gcp-devrel-py-tools==0.0.13
h11==0.8.0
# Temporary pin to work around:
# https://github.com/shazow/urllib3/issues/1340
# https://github.com/shazow/urllib3/issues/1341
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can delete this comment now :-) or drop the pin altogether, idk.

There are services like requires.io and pyup.io that can automatically send PRs to update pins when never versions come out, but I don't know how fancy we want to get here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the comment, thanks!

I think pyup.io/requires.io are a good idea, even if I never tried them. Which one would you choose?

@njsmith
Copy link
Member

njsmith commented Mar 24, 2018

OK cool!

We should also fix it so that import urllib3 can succeed even if trio and twisted aren't installed, but that's a whole other thing...

@njsmith njsmith merged commit d9321ce into python-trio:bleach-spike Mar 24, 2018
@pquentin pquentin deleted the bump-requirements-versions branch March 24, 2018 04:48
@pquentin
Copy link
Member Author

Okay, I added https://github.com/njsmith/urllib3/issues/25 for the import niceties we need.

@njsmith
Copy link
Member

njsmith commented Mar 24, 2018

Oh, sorry, I missed seeing your latest comments.

Re: --failed-first, huh, that does look useful! I don't think I've used it before :-). I guess --random-order-bucket=none --failed-first should still work?

We have pyup.io running on the manylinux repo, and python-hyper uses requires.io... I really don't have any reason to prefer one or the other. They both seem to work fine I guess, though I'm not sure if they can handle our weird branch setup or not.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants