Skip to content

Conversation

@Jeff-Meadows
Copy link
Contributor

The latest version of pytest (3.3.0) dropped support for these
python versions, so we need to install an older version when
we're being run on one of them.

The latest version of pytest (3.3.0) dropped support for these
python versions, so we need to install an older version when
we're being run on one of them.
@Jeff-Meadows Jeff-Meadows requested a review from jmoldow November 29, 2017 05:18
@boxcla
Copy link

boxcla commented Nov 29, 2017

Verified that @Jeff-Meadows has signed the CLA. Thanks for the pull request!

@Jeff-Meadows Jeff-Meadows merged commit 9eb12ac into box:master Nov 29, 2017
@Jeff-Meadows Jeff-Meadows deleted the fix_build_pytest branch November 29, 2017 05:24
@jmoldow
Copy link
Contributor

jmoldow commented Nov 29, 2017

More and more tools are going to be dropping 2.6 support in the future (e.g. pip). At some point we should consider whether we should also drop 2.6 support.

Rather than having conditional Python code inside setup.py, I feel like it would've been better to either:

  • Pin to the same pytest version for all Python versions, for consistent behavior
  • Use a requirements conditional, e.g.
pytest>=2.8.3 ; python_version == '2.7' or python_version > '3.3'
pytest>=2.8.3,<3.3.0 ; python_version == '2.6' or python_version == '3.3'

mattwiller pushed a commit that referenced this pull request Jun 28, 2018
The latest version of pytest (3.3.0) dropped support for these
python versions, so we need to install an older version when
we're being run on one of them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants