Set version number explicitly

[Johannes-Sahlmann]

Minor code developments.

[Johannes-Sahlmann]

@jameswu2 could you please have a look at this PR?

The problem is a stricter checking of versioning in pip (popping up in several places, see e.g. spacetelescope/pystortion#10).

Ideally, one would have to fix the underlying problem, of consistently setting the version number (automatically, when possible).

[jameswu2]

@Johannes-Sahlmann Hi Johannes, my involvement with this project is limited to my role as admin for the GitHub org. Is there anyone else you can request a review from?

[Johannes-Sahlmann]

@tonysohn I hope you are doing well.

Would you have time to have a look at this PR? This package is a dependency of https://github.com/spacetelescope/astrometry-scripts and I hope this issue does not cause problems there, but I did not check.

[tonysohn]

@Johannes-Sahlmann Hi Johannes. I'm doing well here, and hope you are, too. I do have a fixed version myself (https://github.com/tonysohn/uhelpers). But broadly, I actually started an entirely new package based on your scripts. I wanted to have most of the relevant scripts in a single repo with less dependencies. The new script lies at: https://www.github.com/tonysohn/jwst_fpa . Not sure what to do with these scripts you have here...

[Johannes-Sahlmann]

Thanks @tonysohn . What does your fix consist in and why don't you open a pull request to get it into the upstream repo?

Also related, I ran into similar problems with my pystrometry package, which I fixed today (https://github.com/Johannes-Sahlmann/pystrometry).

The problem was that I usually did not do proper releases of my packages (with dev in the version name) and doing that fixes the problems related to the newly-raised pip errors, as far as I can see.