NavList:

Hello Bela,

I have been asked by Frank Reed to move topics that only concern Pyalmanac, SFalmanac or Skyalmanac to my GitHub site. I would welcome any kind of communication in one of my "Issues" GitHub web sites, e.g. here:
https://github.com/aendie/SkyAlmanac-Py3/issues

I found your question good, so I'll try to give you a shorter answer here with less web links (as these messages are automatically rejected by the NavList site).

Today SFalmanac = Skyalmanac. Pyalmanac is the old original code I took from Enno Rodergardts. I created SFalmanac ('Skyfield-based almanac') when I moved from the Ephem (= Pyephem) astronomical library to Skyfield, a modern and elegant astronomical library, both authored by Brandon Rhodes.

Briefly: Skyalmanac was an interim solution with some shortcomings because SFalmanac originally had very poor performance (=speed of execution).
I found a solution to speed it up: I used multiprocessing (as most PCs today have multiple core CPUs).
Now there was no justification for Skyalmanac anymore, however I prefer the name Skyalmanac to SFalmanac... and I noticed new users pick on Skyalmanac first.
So I made them identical (and got rid of the old temporary Skyalmanac hybrid version).
The most up-to-date product is Skyalmanac (=SFalmanac).
Pyalmanac is only for those who wish to remain with the original version, e.g. the author Enno Rodegerdts in his Hallberg-Rassy.

You can read more on my PyPI site:
https://pypi.org/project/skyalmanac/

and my GitHub site:
https://github.com/aendie/Skyalmanac-Py3

I apologise for the confusion, but quite a lot of work has been invested into the development thus far.

Kind Regards, Andrew