Closed John-Ragland closed 6 months ago
@lsetiawan do you have specific suggestions on how we might should change the packaging for ooipy? We've been working on a bigger update to v1.2.0, where we're adding a good bit of functionality. And it'd probably make sense to do this for this update.
Also, this will probably be a good time to get rid of our numpy<1.22 requirement and test that it doesn't break anything.
@John-Ragland just to let you know that the latest version of xarray do require python 3.9 and greater and your package currently is pinned to be >=3.7
, which means that if users installs your package with python 3.7
they won't be using the latest xarray. If ooipy works with python >=3.9
then let's update that and start using python >=3.9 for development.
Here's a recommended guide for developing scientific python package that you should read and follow: https://learn.scientific-python.org/development/. It's made by the greater scientific python community. The specific packaging guide can be found here. It would be a pretty huge overhaul, I can help guide you guys if you'd like to make this happen.
@John-Ragland just to let you know that the latest version of xarray do require python 3.9 and greater and your package currently is pinned to be
>=3.7
, which means that if users installs your package with python3.7
they won't be using the latest xarray. If ooipy works with python>=3.9
then let's update that and start using python >=3.9 for development.
I think that's a good idea. OOIPy should work with 3.9
Originally posted by @lsetiawan in https://github.com/Ocean-Data-Lab/ooipy/issues/147#issuecomment-1650492484