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 support for Python 3.3 #1666

Closed
jaraco opened this Issue Dec 4, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@jaraco
Member

jaraco commented Dec 4, 2017

@jaraco

This comment has been minimized.

Show comment
Hide comment
@jaraco

jaraco Dec 4, 2017

Member

I've force-built this job to cut the release of 12.0.2.

Member

jaraco commented Dec 4, 2017

I've force-built this job to cut the release of 12.0.2.

jaraco added a commit that referenced this issue Dec 4, 2017

@webknjaz

This comment has been minimized.

Show comment
Hide comment
@webknjaz

webknjaz Dec 4, 2017

Member

I'm sure it's safe to just drop 3.3

Member

webknjaz commented Dec 4, 2017

I'm sure it's safe to just drop 3.3

@jaraco jaraco changed the title from Python 3.3 tests failing to Drop support for Python 3.3 Dec 4, 2017

@jaraco

This comment has been minimized.

Show comment
Hide comment
@jaraco

jaraco Dec 4, 2017

Member

Good point. Rather than waiting for upstream pytest to fix their distribution, let's just drop support.

Member

jaraco commented Dec 4, 2017

Good point. Rather than waiting for upstream pytest to fix their distribution, let's just drop support.

@webknjaz

This comment has been minimized.

Show comment
Hide comment
@webknjaz

webknjaz Dec 4, 2017

Member

There's nothing to fix in pytest upstream: they've officially dropped support for 2.6 and 3.3 in their latest release. We can only pin version of this dependency.

Member

webknjaz commented Dec 4, 2017

There's nothing to fix in pytest upstream: they've officially dropped support for 2.6 and 3.3 in their latest release. We can only pin version of this dependency.

jaraco added a commit that referenced this issue Dec 4, 2017

@jaraco

This comment has been minimized.

Show comment
Hide comment
@jaraco

jaraco Dec 4, 2017

Member

There is an upstream bug - the 3.3 release doesn't effectively declare dropped support for 3.3 but its dependency (py) does... so pip attempts to install it and then fails.

Member

jaraco commented Dec 4, 2017

There is an upstream bug - the 3.3 release doesn't effectively declare dropped support for 3.3 but its dependency (py) does... so pip attempts to install it and then fails.

@webknjaz

This comment has been minimized.

Show comment
Hide comment
@webknjaz

webknjaz Dec 4, 2017

Member

Oh, I see. But it doesn't change the fact that 3.3 isn't supported anymore :)

Member

webknjaz commented Dec 4, 2017

Oh, I see. But it doesn't change the fact that 3.3 isn't supported anymore :)

@jaraco jaraco closed this in #1668 Dec 4, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment