Improve setup and change source code layout to comply with PEP-660.

[jlenain]

Following @maxnoe 's path on ctapipe_io_lst, this PR proposes to improve the setuptools configuration to comply with PEP-660.

[codecov]

Codecov Report

Base: 96.05% // Head: 87.05% // Decreases project coverage by -9.00% ⚠️

Coverage data is based on head (dec1072) compared to base (c17671c).
Patch coverage: 100.00% of modified lines in pull request are covered.

❗ Current head dec1072 differs from pull request most recent head d71e274. Consider uploading reports for the commit d71e274 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
- Coverage   96.05%   87.05%   -9.00%     
==========================================
  Files           8        7       -1     
  Lines         228      510     +282     
==========================================
+ Hits          219      444     +225     
- Misses          9       66      +57     

Impacted Files	Coverage Δ
src/ctapipe_io_nectarcam/__init__.py	80.75% <ø> (ø)
src/ctapipe_io_nectarcam/anyarray_dtypes.py	100.00% <ø> (ø)
src/ctapipe_io_nectarcam/calibration.py	100.00% <ø> (ø)
src/ctapipe_io_nectarcam/constants.py	100.00% <ø> (ø)
src/ctapipe_io_nectarcam/containers.py	100.00% <ø> (ø)
src/ctapipe_io_nectarcam/_dev_version/__init__.py	100.00% <100.00%> (ø)
src/ctapipe_io_nectarcam/version.py	100.00% <100.00%> (ø)
...pe_io_nectarcam/tests/test_nectarcameventsource.py
src/ctapipe_io_nectarcam/tests/test_version.py
... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[maxnoe]

The package name on pypi is tables, without the py

[maxnoe]

Conda calls it pytables though (so it is correct in environment.yml)

[jlenain]

Thanks a lot, @maxnoe ! How mean...

[dkerszberg]

The change seems to work on my side. @frnbrun ca you confirm it fixed the problem you reported in cta-observatory/nectarchain#28 ?

@jlenain I see one test failed with:
FAILED src/ctapipe_io_nectarcam/tests/test_version.py::test_version - AssertionError: assert '0.0.0' != '0.0.0'
It seems to be related with your change of version (which is a good idea I agree :-) ), can we remove the test on the version or update it to something that won't fail (I didn't check at all what is done there tbh)?

[maxnoe]

@dkerszberg the test fails because there is no tag yet in this repository. Either switch it off for the time being, or create an 0.1.0 tag on the master before merging this.

[jlenain]

Hi @dkerszberg,
Thanks for the feedback!
Indeed, as pointed out by @maxnoe , this test error will vanish as soon as we start tagging the code. I'd prefer to keep this mechanism in place, which is actually based on the implementation e.g. from astropy, ctapipe, or ctapipe_io_lst, since it is meant to automatize and ease release management.

[dkerszberg]

Thank you both for the clarification! I see @jlenain already clarified in the other thread that it fixes the issue from @frnbrun so I'm ready to do the merge. I'll just wait until tomorrow in case @frnbrun wants to have a look :-)

[dkerszberg]

Ready to be merged

[frnbrun]

Thanks @jlenain and @dkerszberg !