modernize packaging

[ocefpaf]

Use setuptools_scm instead of versioneer and pyproject.toml instead of setup.*.

Only review this one after #136 is sorted out.

[ocefpaf]

@ajdawson let me know if you need help navigating this PR. Sorry I ended up bloating it but this will get the CIs back online/

[ocefpaf]

@ajdawson I replaced this test with pre-commits. We can add more checks there if you want but I would do that in another PR to avoid bloating this one more than it already is.

[ajdawson]

This is fine I think

[ocefpaf]

Using setuptools_scm instead of versioneer b/c that one is better maintained and "blessed" by the Python packaging community.

[ocefpaf]

This replaces both setup.py and setup.cfg with "modern" python packaging practices.

[ocefpaf]

To support all the extras on Windows and Python 3.11 we would need to drop cdms2.
xref.: conda-forge/cdms2-feedstock#80 (comment) and conda-forge/cdtime-feedstock#52 (comment)

[ajdawson]

Maybe the time is coming to remove the cdms2 interface in this module...

[ajdawson]

But we can leave it like this for now and deal with that separately.

[ocefpaf]

Twine check is failing with:

Checking eofs-0.1.dev1+g23a45fe-py3-none-any.whl: FAILED
ERROR    `long_description` has syntax errors in markup and would not be        
         rendered on PyPI.                                                      
         No content rendered from RST source.                                   
WARNING  `long_description_content_type` missing. defaulting to `text/x-rst`.   
Checking eofs-0.1.dev1+g23a45fe.tar.gz: PASSED with warnings
WARNING  `long_description_content_type` missing. defaulting to `text/x-rst`.   
WARNING  `long_description` missing.                                            
Error: Process completed with exit code 1.

I can reproduce that locally and I see that it still packages the deleted setup.cfg, no idea why/how that id happening :-/

---

Edit: I missed an entry for the dynamic README and it should be fixed in 30cc5c8.

[ajdawson]

Ok, so again I won't pretend that I understand every part of this, but I think this is going in the right direction so I will be happy to merge it. Thanks for the hard work (and it does look like quite a lot of work!). I'm not sure about the pypi secrets, you'll have to fill me in on what needs to be done there.

[ocefpaf]

I'm not sure about the pypi secrets, you'll have to fill me in on what needs to be done there.

You will need to:

1. In your PyPI account settings, scroll down to the "add API token" button

I usually name it <pkgname>__token__ and choose the scope of the package only.

2. In you GitHub settings for eofs go to Secrets and Variables → Actions → and create a Repository secret named PYPI_PASSWORD with the token value you got from 1.

PS: There is also the Trusted Publisher route but I did not try that one yet.

[ajdawson]

Sorry that took so long @ocefpaf, was locked out of PyPI account when I went to resolve this back in June, and then just forgot about it. I think this should all be set up properly now. Thanks for the effort!