jplhorizons epochs kwarg should accept Time objects
Open
enhancement
jplhorizons
- Dominant language
- Python
- Stars
- 791
- Forks
- 451
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 4
Description
`'epochs'` should be `Time` objects or at least be able to accept `Time` objects.
Some discussion was here: #1488
Contributor guide
Research direction
Start with the discussion in #1488, then locate the JPL Horizons query entry point that handles the `epochs` kwarg. Establish the expected behavior for `Time` objects from that discussion; done means the kwarg accepts them as requested and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100