Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Coordinates “performance vs correctness” tradeoff option #8407

Open
pllim opened this issue Feb 8, 2019 · 2 comments
Open

Coordinates “performance vs correctness” tradeoff option #8407

pllim opened this issue Feb 8, 2019 · 2 comments
Assignees
@eteq
Labels
coordinates Performance

Comments

@pllim
Copy link
Member

pllim commented Feb 8, 2019 •
edited

This is one of the 3.2 features mentioned in Astropy Coordination Meeting 2018.

p.s. I am guessing it is a documentation issue, but if I misunderstood, feel free to edit.
@pllim pllim added this to the v3.2 milestone Feb 8, 2019
@bsipocz
Copy link
Member

bsipocz commented Feb 8, 2019

Some of it may very well be code related, e.g. #6068

@pllim pllim removed the Docs label Feb 8, 2019
@pllim pllim changed the title DOC: Coordinates “performance vs correctness” tradeoff option Coordinates “performance vs correctness” tradeoff option Feb 8, 2019
@pllim
Copy link
Member Author

pllim commented Apr 17, 2019

@eteq or @adrn , any chance of this happening before 3.2 feature freeze?

@bsipocz bsipocz removed this from the v3.2 milestone Apr 20, 2019
@bsipocz bsipocz mentioned this issue Apr 30, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eteq eteq

Labels
coordinates Performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@eteq @pllim @bsipocz