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

Consider exposing ERFA as part of public API #3123

Open
astrofrog opened this Issue Nov 21, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@astrofrog
Member

astrofrog commented Nov 21, 2014

This is non-urgent, but it might be worth considering in future whether the ERFA package with the Python wrapers is part of the public API, and if so, we should add an entry to the documentation about it (and an auto-generated API list). But it makes sense to wait until we've ironed out any issues while making use of it in coordinates.

I know there is interest to provide higher level wrappers with more explicit names, but it doesn't mean the lower-level API can't also be available.

@astrofrog astrofrog added the erfa label Nov 21, 2014

@astrofrog astrofrog added this to the Future milestone Nov 21, 2014

@astrofrog astrofrog changed the title from Consider exposing ERFA as part of API to Consider exposing ERFA as part of public API Nov 21, 2014

@mhvk

This comment has been minimized.

Show comment
Hide comment
@mhvk

mhvk Mar 2, 2016

Contributor

Probably worth reviving this given the wrapping of angle operations and spherical functions in #4571. My vote would be for exposure in a separate pyerfa (or so) package which is part of liberfa, and which we use as an external package in astropy.

Contributor

mhvk commented Mar 2, 2016

Probably worth reviving this given the wrapping of angle operations and spherical functions in #4571. My vote would be for exposure in a separate pyerfa (or so) package which is part of liberfa, and which we use as an external package in astropy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment