Skip to content

Conversation

seratch
Copy link
Contributor

@seratch seratch commented Jun 4, 2020

Summary

This pull request fixed #53 by removing python 2.7.6 from CI builds.

Requirements (place an x in each [ ])

@seratch seratch added the tests M-T: Testing work only label Jun 4, 2020
@seratch seratch requested a review from stevengill June 4, 2020 12:01
@seratch
Copy link
Contributor Author

seratch commented Jun 4, 2020

After merging this PR, I will check the existing mergeable PRs.

@seratch
Copy link
Contributor Author

seratch commented Jun 4, 2020

Ah, we need to repair the build settings first. I will work on it.

@seratch seratch changed the title Fix #53 by removing python 2.7.6 from TravisCI builds WIP: Fix #53 by removing python 2.7.6 from TravisCI builds Jun 4, 2020
@seratch seratch changed the title WIP: Fix #53 by removing python 2.7.6 from TravisCI builds Fix #53 by removing python 2.7.6 from TravisCI builds Jun 8, 2020
testfixtures==5.3.1
tox==2.9.1
tox==2.9.1
werkzeug==0.16.1
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is a quick (and tentative) fix for ImportError: cannot import name 'cached_property' from 'werkzeug' (incompatibility with werkzeug 1.0), which is not an issue of this library.

see also: jarus/flask-testing#143

Copy link
Contributor

Choose a reason for hiding this comment

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

Is werkzeug a transitive dependency through some other dependency? I'm not sure how this affected our package.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@aoberoi
Flask depends on werkzeug. Flask's project setting has been declaring it is compatible with Werkzeug>=0.15 for a long time.

As mentioned above (and also you can see the actual failure here), werkzeug 1.0 is incompatible with 0.16 or older as it has removed cached_property module.

As far as I know, the breaking change affects only tests with Flask. I haven't found any issues with production apps yet. I will verify if there is really no issue. I'm going to check which versions of Flask this package should support soon in regards to #58

On the assumption that the breaking change doesn't directly affect this package, I just applied a quick fix to run tests with werkzeug 0.16. In my observation, it's safe enough.

Does this make sense to you?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

#72 removed this limitation

@seratch seratch requested a review from aoberoi June 8, 2020 05:16
@seratch
Copy link
Contributor Author

seratch commented Jun 8, 2020

@stevengill @aoberoi This PR is ready for review.

@seratch
Copy link
Contributor Author

seratch commented Jun 9, 2020

I'll merge this PR tomorrow.

@seratch seratch merged commit 04e806b into slackapi:master Jun 10, 2020
@seratch seratch deleted the issue-53 branch June 10, 2020 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests M-T: Testing work only
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Proposal: Remove Python 2.7.6 support
3 participants