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

Have our next release be 9.0 instead of 8.2 #4047

Merged
merged 1 commit into from
Oct 30, 2016
Merged

Conversation

dstufft
Copy link
Member

@dstufft dstufft commented Oct 30, 2016

Closes #3955
Closes #3962

@RonnyPfannschmidt
Copy link
Contributor

@dstufft so pip is entering the python 2.6 is deprecated epoch, should we follow suit in pytest or just drop 2.6 at the next major of pip

@dstufft
Copy link
Member Author

dstufft commented Oct 30, 2016

Y'all can do whatever makes the most sense for y'all. Including dropping support earlier. Worst case we can pin the version for 2.6.

Sent from my iPhone

On Oct 30, 2016, at 5:22 PM, Ronny Pfannschmidt notifications@github.com wrote:

@dstufft so pip is entering the python 2.6 is deprecated epoch, should we follow suit in pytest or just drop 2.6 at the next major of pip


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@dstufft dstufft merged commit c3dc757 into pypa:master Oct 30, 2016
@dstufft dstufft deleted the rev-to-9 branch October 30, 2016 22:09
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Drop support for Python 2.6?
3 participants