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 2.6 and 3.3 #288

Closed
mwcraig opened this Issue Jan 25, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@mwcraig
Contributor

mwcraig commented Jan 25, 2016

We should definitely drop 2.6. I don't see much point in continued support for 3.3. Would help address the fails in #287

@mwcraig mwcraig added the question label Jan 25, 2016

@mwcraig mwcraig added this to the 0.4 milestone Jan 25, 2016

@crawfordsm

This comment has been minimized.

Show comment
Hide comment
@crawfordsm

crawfordsm Jan 28, 2016

Member

Agreed.

Member

crawfordsm commented Jan 28, 2016

Agreed.

@mwcraig mwcraig added tests and removed question labels Feb 2, 2016

@crawfordsm

This comment has been minimized.

Show comment
Hide comment
@crawfordsm

crawfordsm Feb 9, 2016

Member

closed by #287

Member

crawfordsm commented Feb 9, 2016

closed by #287

@crawfordsm crawfordsm closed this Feb 9, 2016

@bsipocz

This comment has been minimized.

Show comment
Hide comment
@bsipocz

bsipocz Feb 9, 2016

Member

@crawfordsm @mwcraig - Does this issue also means that the 2.6 workarounds can/should be removed?

Member

bsipocz commented Feb 9, 2016

@crawfordsm @mwcraig - Does this issue also means that the 2.6 workarounds can/should be removed?

@mwcraig

This comment has been minimized.

Show comment
Hide comment
@mwcraig

mwcraig Feb 9, 2016

Contributor

Yes, that would make sense.

Contributor

mwcraig commented Feb 9, 2016

Yes, that would make sense.

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