Repository navigation
Bump minimum Numpy version to 1.4 - #70
Conversation
|
I think this makes sense. I've had issues with 1.3 in the past for structured arrays, and these are going to be used in |
|
The only issue I can see is that the last Ubuntu LTS release ships with 1.3. But the next LTS release is 12.04...which is probably sooner than we're likely to see significant Astropy adoption. So I don't see it as a likely issue... |
|
What about having a setup.py flag to force installation regardless of dependencies? That way, |
|
I don't really care either way, but that would be easy to add if others think it's a good idea. |
|
In any case I agree with not supporting 1.3 by default. |
|
I vaugely prefer just requiring 1.4 because that'll be simpler/more-standard, but I'm fine with either solution. |
Bump minimum Numpy version to 1.4
Bump minimum Numpy version to 1.4
Alternate fix for astropy#68
added method to set coord_type
Added Travis to validate JSON file
1.3 has some problems with byteswapping complex numbers that makes supporting them in
io.voalmost impossible. I know @iguananaut had mentioned that 1.3 support for the upcomingio.fitsis also annoying. Should we just bite the bullet and drop 1.3?