Astropy Affiliated Package Review about omnifit

[RiceMunk]

Alright, good to know. Actually have a bit of time to work on this today, so been transitioning the PR to use the new (at least compared to what omnifit master uses now) astropy package template instead of astropy_helpers.

My intent is to try and get the fixes implemented in such a way that I can automate most of the build/release checking on my end and not have to intervene much in package maintenance in the future, unless some dependency updates end up breaking the whole thing.

I can't promise that I'll do anything about e.g. the mentioned astropy ecosystem integrations in a reasonable timeframe, though. If I end up touching Omnifit to that degree, there's a number of other improvements I'd rather do first as by my current standards I'm not terribly happy with its fitting methodology in the first place. But that's a bigger issue to tackle.

[dhomeier]

Thank you again for your ongoing efforts to keep this package up to date @RiceMunk.
As mentioned the requirements for becoming an affiliated package include, since last year, support of Python 3.
For existing affiliated packages that do not yet meet this requirement, there is a 6 month period to add Python 3 compatibility in order to retain their affiliated status.
Since the code in #43 already fully supports Python 3.10, I am confident that the package will be able to meet this goal by July.