Migrate packaging configuration to pyproject.toml

[LOCEANlloydizard]

Following the migration of echopype and echoregions to pyproject.toml, we should homogenise and migrate echopop to pyproject as well!

[brandynlucca]

Are you referring to just this pyproject.toml? If so, Echopop already uses it.

[LOCEANlloydizard]

ops my bad, I looked too quickly! I saw the files (requirements.txt, requirements-dev.txt, etc.) and didn’t check more.. Maybe we could remove those to avoid duplicate dependency declarations?

And we could also update the URL to reflect the recent organisation name change :)

[leewujung]

I think there was a point of time both are needed for the packing to work out, but i am not sure when @brandynlucca added the pyproject.toml.

Maybe as part of this we can separate the regular and dev into different sections of pyproject.toml to keep things tidy?

[brandynlucca]

Maybe we could remove those to avoid duplicate dependency declarations?

They sort of serve different purposes, although there are new pylock.toml files that I haven't really used. I tried deprecating requirements.txt, but that causes a few of the GH Actions to break (and I think I was running into a Conda issue for it as well). The other issue is that there are a few dependencies in requirements-dev.txt that have some compatibility issues.

[leewujung]

This would be a great item for the hack today!

Somehow I didn't run into problems with pyproject.toml only for echodataflow, but it could also be that the codebase has a lot less dependencies (and there's no GH actions yet!) - though @LOCEANlloydizard you migrated the GH actions in echopype with pyproject.toml right? And for the dev dependencies yet we would have to check them then....

[LOCEANlloydizard]

Alright, I’ve proposed a PR to address this, based on what was done for echopype/echoregions. Let’s see if the CI passes! Cheers!