Repository navigation
Final what's new in 1.0 changes - #3451
Conversation
|
@eteq - how did you derive these values before: Do you have a script? Can we add something similar here? Do we include v0.4.1 to v0.4.4 in the numbers? |
|
@astrofrog - Honestly I don't remember. I think I had some hacked together thing to grab the stats from the github API. Something like https://github.com/astropy/astropy-tools/blob/master/gitastropyplots.py but with a check for when exactly it happened. |
|
Incidentally, I just ran and got Should astropy-helpers support Python 3.2? I can't remember if there has been a decision on that point or not. If it needs to it could. If it doesn't need to it should still give a nicer error message instead of just blowing up at the first occasion something doesn't work. |
eb29e9b to
dce7979
Compare
|
@embray - I implemented your comments, thanks! Regarding Python 3.2, I think it's fine to not support it (I thought that by deciding to not support astropy for 3.1 or 3.2 that decision automatically extended to astropy-helpers). Are you thinking that we should raise an error like |
dce7979 to
09ba430
Compare
|
Looks good, so I'm going to go ahead and merge. We can add the number of issues closed section just before release so it has the latest numbers. A agree no need to support py 3.2 in the helpers if we're not going to support it in astropy (unless some affiliated package specifically needs it, and I can't imagine that's true right now). |
One last small change before 1.0rc2