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

Jump to bottom

Set up travis to test 3.4/drop 3.2 #3090

Closed
tacaswell opened this issue May 27, 2014 · 2 comments · Fixed by #3192
Closed

Set up travis to test 3.4/drop 3.2 #3090

tacaswell opened this issue May 27, 2014 · 2 comments · Fixed by #3192
Labels
Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Milestone
v1.4.0

Comments

@tacaswell
Copy link
Member

Can we drop 3.2 to lighten the testing burden?
@tacaswell tacaswell added this to the v1.4.0 milestone May 27, 2014
@mdboom
Copy link
Member

mdboom commented May 27, 2014

I think that's reasonable. In astropy, we've kept 3.2, dropped 3.3 and added 3.4 (because 3.3 and 3.4 are more similar in a lot of ways). But I'm also fine with dropping 3.2 completely -- I can't imagine the installed base is very large there.

@efiring
Copy link
Member

efiring commented Jul 6, 2014

Dropping 3.2 is fine with me.

@tacaswell tacaswell mentioned this issue Jul 6, 2014
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Projects
None yet
Milestone
v1.4.0
Development

Successfully merging a pull request may close this issue.

TST : drop 3.2, add 3.4 tacaswell/matplotlib
3 participants
@mdboom @efiring @tacaswell