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.

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

Drop python 3.4 #803

Merged
merged 2 commits into from
Jul 24, 2019
Merged

Drop python 3.4 #803

merged 2 commits into from
Jul 24, 2019

Conversation

auvipy
Copy link
Contributor

@auvipy auvipy commented May 2, 2019

Remove py34 from:

  • setup
  • tox
  • appveyour
  • travis

@vphilippon vphilippon added this to the 3.7.0 milestone May 2, 2019
Copy link
Member

@atugushev atugushev left a comment

Choose a reason for hiding this comment

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

Hello @auvipy,

Thank you for the contribution! I would rather not to drop the support. I think we should wait at least a pip release (it should be right after 19.1) with dropped support of the python 3.4 and after, we could drop the support and make a release for the pip-tools.

But since we have already removed the support in #804 and #805 (why they are not approved, but merged by the way, @auvipy?) my concerns may not reasonable anymore.

@vphilippon @blueyed what do you think?

@auvipy
Copy link
Contributor Author

auvipy commented May 3, 2019

https://github.com/pypa/pip/releases/tag/19.1 is already on the wild 💃

@atugushev
Copy link
Member

atugushev commented May 3, 2019

https://github.com/pypa/pip/releases/tag/19.1 is already on the wild 💃

19.1 still supports 3.4 with a deprecation warning and support will gone since 19.2.

@auvipy
Copy link
Contributor Author

auvipy commented May 3, 2019

Hello @auvipy,

Thank you for the contribution! I would rather not to drop the support. I think we should wait at least a pip release (it should be right after 19.1) with dropped support of the python 3.4 and after, we could drop the support and make a release for the pip-tools.

But since (as i can see in the master branch) we have already removed the support in #804 and #805 (why they are not approved, but merged by the way, @auvipy?) my concerns may not reasonable anymore.

@vphilippon @blueyed what do you think?

IMHO, as it's not breaking anything and a very trivial valid change, these shouldn't go through the full formal process always, since practicality beats purity. And we can revert again if that creates a problem. but I didn't merge anything with Red Button 🗡️

@codecov
Copy link

codecov bot commented May 5, 2019

Codecov Report

Merging #803 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #803   +/-   ##
=======================================
  Coverage   98.78%   98.78%           
=======================================
  Files          35       35           
  Lines        2050     2050           
  Branches      262      262           
=======================================
  Hits         2025     2025           
  Misses         15       15           
  Partials       10       10

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c45998a...ab39ec4. Read the comment docs.

@codecov
Copy link

codecov bot commented May 5, 2019

Codecov Report

Merging #803 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #803      +/-   ##
==========================================
- Coverage   98.78%   98.77%   -0.01%     
==========================================
  Files          35       35              
  Lines        2050     2044       -6     
  Branches      262      262              
==========================================
- Hits         2025     2019       -6     
  Misses         15       15              
  Partials       10       10
Impacted Files Coverage Δ
tests/test_utils.py 100% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c45998a...ab39ec4. Read the comment docs.

@atugushev atugushev changed the title Drop python 3.4 from setup Drop python 3.4 May 5, 2019
@atugushev atugushev added the maintenance Related to maintenance processes label May 5, 2019
@atugushev
Copy link
Member

atugushev commented May 5, 2019

@auvipy

IMHO, as it's not breaking anything and a very trivial valid change, these shouldn't go through the full formal process always, since practicality beats purity. And we can revert again if that creates a problem. but I didn't merge anything with Red Button

It's not a problem, but I would prefer to be more collaborative (even on trivial changes) :) See also jazzband/help#121 (comment).

PS
It's been forgotten to drop support from appveyour, so i've fixed it.

PPS
But i still think we should drop support after pip==19.2 release.

@auvipy
Copy link
Contributor Author

auvipy commented May 5, 2019

I do agree with you buddy!

@atugushev atugushev removed this from the 3.7.0 milestone May 9, 2019
@atugushev
Copy link
Member

atugushev commented May 9, 2019

I've removed the current milestone to prepare new release.

@auvipy
Copy link
Contributor Author

auvipy commented May 9, 2019

that's alright

@atugushev atugushev added this to the 3.10.0 milestone Jul 24, 2019
@atugushev atugushev merged commit 6a116c7 into master Jul 24, 2019
@atugushev atugushev deleted the auvipy-patch-1 branch July 24, 2019 13:10
@atugushev atugushev modified the milestones: 3.10.0, 4.0.0 Jul 24, 2019
@atugushev
Copy link
Member

Since we drop 3.4 support i'd suggest to bump major version.

@atugushev atugushev added deprecation Related to deprecations or removals and removed maintenance Related to maintenance processes labels Jul 25, 2019
@atugushev
Copy link
Member

pip-tools v4.0.0 is released.

@jdufresne jdufresne mentioned this pull request Dec 16, 2020
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deprecation Related to deprecations or removals
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants