-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Misc cleanup before 2.0 release #120
Conversation
@bsipocz - Do you remember what the fix was to suppress this |
Because of the list intersphinx issue, for now I've just allowed Sphinx warnings in the Python 2 docs build: 32fceb7 |
@cdeil - probably the simplest is to add them as exceptions to a docs/nitpick-exceptions file. |
btw, I'm doing a new helpers release right now, if you want to included that here (though probably nothing major is in there that would affect pyregions). |
I don't think there's a reason to do a helpers update for this package. |
It looks like changes to |
at all? That case I can remove it from the auto-update list. |
I'll check on the conftest stuff soon. |
I would suggest to keep this package on the astropy-helpers update list. I'm just saying if there are no known issues with what we have and CI is all green and this package is already at a recent astropy-helpers v2, then it's OK to release here and have other astropy-helpers updates and other fixes in future releases, no? |
@cdeil - This is what I get:
|
I put this in
and I still get this, which I think is what Astropy has:
Why? |
It inherits the default from astropy, not sure what happens if you try to override that variable, it seems that nothing, you can't override it.
|
Yes, Astropy keeps getting new dependencies (like pandas now) that are not a dependency in affiliated packages. IMO it's simpler / cleaner to just have a separate / independent list here, instead of doing additions / deletions wrt Astropy core and having to change that over time. Obviously this is not a big deal. If it's not clear how to do the list from scratch, I'll go back to the other scheme. @astrofrog - Maybe you have a tip? |
OK, then it's really an issue for the package template. What I would do is to hack around with a list to keep and clear the dict automatically for everything else. |
Hmm, actually, this can be fixed in astropy. The dict is defined separately in the plugin, and there is indeed no reason to keep pandas or h5py or any astropy specific entry there. I would suggest to keep numpy and mpl there, but even the latter could be removed from the default one. |
@bsipocz - I followed your suggestion to clear the dict and then fill it how I like. Works fine. Thanks! Thinking about it a bit, it's not really surprising that making a new |
ds9_shape_in_comment_defs = dict( | ||
text=wcs_shape(CoordOdd, CoordEven), | ||
vector=wcs_shape(CoordOdd, CoordEven, | ||
Distance, Angle), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no need for these line breaks any more
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(ohh, never mind, haven't seen that this got merged in the meantime ;) )
I plan to do some misc fixes and cleanup here, before the 2.0 release.
Currently there are some fails in master:
https://travis-ci.org/astropy/pyregion/builds/287512820
If there's anything difficult or controversial, I'll ask. No need to review at this point.
Work in progress ...