APE23 Discussion

[Kyle Westfall]

Hi all,

APE 23 is now ready for discussion.

Following the new procedures in APE 1, APE 23 has been merged into the
main branch of the repo and further discussion of the repo should happen
here, on the astropy-dev mailing list.

You can see the original PR here:
https://github.com/astropy/astropy-APEs/pull/112

You can find APE23 here:
https://github.com/astropy/astropy-APEs/blob/main/APE23.rst

The discussion period should last for at least two weeks (ending no
earlier than 10 Feb), after which the authors may submit a PR with a
revised version that incorporates the discussion.  Once that PR is
merged (or if an additional PR is not necessary), the authors will
notify the CoCo that the APE is ready for final review.

Thanks,
Kyle

[Kyle Westfall]

Hi all,

I think this message was moderated and only released today.  Let's extend the discussion period to end no earlier than 13 Feb.

Also, I was supposed to include a short summary of the APE!  Here's the title and a copy of the abstract:


APE23: Removing data storage (representations) from coordinate frames

Following the rationale presented in APE 5, coordinate frames in astropy.coordinates currently store metadata used to construct the frame (i.e., for transforming between frames) and may also store coordinate data itself. This duplicates functionality with SkyCoord, which acts as a container for both coordinate data and reference frame information. We propose to change the frame classes such that they only store metadata and never coordinate data, superseding this aspect of the implementation in APE 5. This would make the implementation more modular and performant, remove ambiguity for users from having nearly duplicate functionality with slightly different APIs, and better satisfy the principle of Separation of Concerns.


Thanks,
Kye