search

astrofrog / wcsaxes

wcsaxes has been merged into astropy!
http://docs.astropy.org/en/stable/visualization/wcsaxes/index.html
22 stars 21 forks source link

Updating to package template 1.1.2 #207

Closed bsipocz closed 8 years ago

bsipocz commented 8 years ago

Includes configparser changes at both places for python 3.5.2

bsipocz commented 8 years ago

I still have two sphinx warnings locally, and don't really know what to do with them:

WARNING: FITSFixedWarning: LONPOLE2= 180.000000000 /lonpole 
invalid alternate code, keyword resembles LONPOLEa but isn't. [astropy.wcs.wcs]
WARNING: FITSFixedWarning: LATPOLE2= 0.00000000000 /latpole 
invalid alternate code, keyword resembles LATPOLEa but isn't. [astropy.wcs.wcs]
astrofrog commented 8 years ago

@bsipocz - I think we just need to fix the data in the data.astropy.org repo (however I'm not sure if those warnings ever caused sphinx to fail before?)

bsipocz commented 8 years ago

Weird, they don't fail travis :)

However numpy 1.6 does, as we build it with the stable astropy. We can use astropy 1.1 in that build if you want to keep it, or can remove it?

astrofrog commented 8 years ago

@bsipocz - thanks! One small request - since 1.1.1post isn't actually a package-template release, can you rephrase the commit message to just say 'to the latest developer version of package-template'? Alternatively, I think it would be best to actually tag 1.1.2 in the package-template. If I do that, can you update the commit message to then say 1.1.2? (I think it would make it easier in future if we tag the package-template whenever we want to apply the changes to packages, to make it easier to refer to versions)

bsipocz commented 8 years ago

Calling it simply the latest dev version is not very helpful I think, but tagging the template before mass applying sounds like a good plan. The configparser changes are critical enough to justify 1.1.2 anyway :)

astrofrog commented 8 years ago

@bsipocz - ok, I'll tag it later today (tags in the package-template are easy enough to do, unlike a core package release!). I just need to update the changelog first.

astrofrog commented 8 years ago

@bsipocz - I tagged v1.1.2, I'll announce it on the affiliated package maintainer mailing list later.

astrofrog commented 8 years ago

@bsipocz - thanks!