Replace tess-locator with tesswcs

[altuson]

• Updated predict() function: uses tesswcs instead of tess-locator to determine the pixel location.
• Created from_sector() function that allows you to initialize a TessEphem object with a target and sector.
• In query to JPL Horizons, return astrometric RA, Dec instead of apparent RA, Dec.
• Updated and added examples to README file.
• Added tests to test_ephem.py for new functions.

[altuson]

I've run pytests, black and flake8 locally so these should pass.

[jorgemarpa]

GH actions are failing because these were defined with python = 3.8 and now the TOML file asks for 3.9.
Is 3.9 necessary because of something specific or can we keep 3.8?

[jorgemarpa]

I've updated the actions in the main brunch. Now you have to pull from upstream in your local branch (tess-wcs) to get the updates. Then push to your branch to update the PR.
That should fix the errors on mypy and black8. You have to run black again before pushing to fix one file formatting.
Also, now it will run pytest when making a new PR.

[altuson]

I've updated the actions in the main brunch. Now you have to pull from upstream in your local branch (tess-wcs) to get the updates. Then push to your branch to update the PR. That should fix the errors on mypy and black8. You have to run black again before pushing to fix one file formatting. Also, now it will run pytest when making a new PR.

@jorgemarpa I have merged your changes into my tess-wcs branch and run black locally to update the file. It should be ready for you to run the workflows and merge with the main branch.

[jorgemarpa]

@altuson: the actions did not pass because Poetry changed how to install developer dependencies, it works as a group now. In the pyproject.toml file, you updated to the new way to group dependencies, this is great! But it made the workflows crash as they were not installing the devs dependencies.
I fix this in the action files and it should run fine now.

Now you should pull from the upstream/main branch these changes to update your branch and the PR.

Sorry we are running into all these small issues. These are because we haven't updated this repo in a while, so many things have changed a bit from last time.

This would be the last one 🤞🏾

[altuson]

@altuson: the actions did not pass because Poetry changed how to install developer dependencies, it works as a group now. In the pyproject.toml file, you updated to the new way to group dependencies, this is great! But it made the workflows crash as they were not installing the devs dependencies. I fix this in the action files and it should run fine now.

Now you should pull from the upstream/main branch these changes to update your branch and the PR.

Sorry we are running into all these small issues. These are because we haven't updated this repo in a while, so many things have changed a bit from last time.

This would be the last one 🤞🏾

@jorgemarpa I've merged the new changes into this branch. Fingers crossed it all runs smoothly now!

[jorgemarpa]

@altuson we are very close now. The action errors are due to different python syntax between 3.9 and 3.10 for the type hints of a function that accepts two types of variables for an argument. I suggest using Optional from typing to avoid this error. See my recommended code line in the files.

[altuson]

@altuson we are very close now. The action errors are due to different python syntax between 3.9 and 3.10 for the type hints of a function that accepts two types of variables for an argument. I suggest using Optional from typing to avoid this error. See my recommended code line in the files.

@jorgemarpa I have made your suggested update.

[jorgemarpa]

LGTM!
merging...