Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Drop Python 3.5 in the CI configuration #4732

Closed
Gallaecio opened this issue Aug 17, 2020 · 1 comment · Fixed by #4743
Closed

Drop Python 3.5 in the CI configuration #4732

Gallaecio opened this issue Aug 17, 2020 · 1 comment · Fixed by #4743
Assignees
@elacuesta
Labels
CI cleanup
Milestone
2.4

Comments

@Gallaecio
Copy link
Member

Gallaecio commented Aug 17, 2020 •
edited
Loading

Any coverage drop may indicate Python 3.5-specific code that can now be removed, either as part of this change or as part of #4733.
@Gallaecio Gallaecio added this to the 2.4 milestone Aug 17, 2020
@Gallaecio Gallaecio mentioned this issue Aug 20, 2020
Merged
@Gallaecio
Copy link
Member Author

For PyPy, I think we should support 7.2.0 as minimum version, given that’s the first version where 3.6 support went out of beta.

@elacuesta elacuesta mentioned this issue Aug 20, 2020
Merged
@rennerocha rennerocha mentioned this issue Aug 31, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@elacuesta elacuesta

Labels
CI cleanup
Projects
None yet
Milestone
2.4
Development

Successfully merging a pull request may close this issue.

Remove py35 from CI elacuesta/scrapy
2 participants
@Gallaecio @elacuesta