Issue with pyproject.toml

[stevehadd]

I'm not entirely sure what the problem is, but I've gotten errors a few times in the last week or so when trying to install pyearthtools using
pip install -e . from the root dir of the repo, but it works OK if I instead use the command pip install -r requirements.txt.

The error i get seems to be around version mismatches. This is my output when I tried running this on ARE-NCI

Obtaining file:///home/005/sh7673/prog/pet_fork
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build editable ... done
  Installing backend dependencies ... done
  Preparing editable metadata (pyproject.toml) ... done
INFO: pip is looking at multiple versions of pyearthtools to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement pyearthtools-data>=0.6.1 (from pyearthtools) (from versions: 0.2.0, 0.5.0, 0.5.1, 0.6.0)
ERROR: No matching distribution found for pyearthtools-data>=0.6.1

This came up for the first time when I tried running pyearthtools on Google Colab, where you need to install the library from git hub as follows:
pip install https://github.com/ACCESS-Community-Hub/PyEarthTools.git
and it failed with the same error message as above.

[stevehadd]

Wasn't sure what the process of assigning issues is @tennlee so tagging you so you can see the issue.

[tennlee]

Thanks Stephen. I see the issue but I need to know a little more about what you're trying to achieve. In particular, I need to know if you're trying to set people up with an editable installation from source code, or just a regular package installation from the wheels.

The problem relates to what's on pypi, what's from source, and what's in 'develop'. It's possible that instead of installing from github, you might want to install from pypi with "pip install pyearthtools". That will install the package, but won't give you an editable installation based on local source code.

That said, the issue still remains for those installing from github. I have two options to fix it, and I actually don't know which is correct.

One option is to have the entries in the top-level pyproject.toml depend on the the PyPI packages, and downgrade the version by 0.1 to the last release (rather than being set to the version tracked on develop). This will work fine, but then users will get a wheel installation rather than an editable source installation, based on the last tag.

The other is to have the entries in the top-level pyproject.toml install from github. This will work fine, but then users will get a wheel installation rather than an editable source installation, based on what is current in 'develop' including latest changes.

I can't work out how to make it seamless for users. That's why the requirements.txt even exists - for developers. Perhaps the easiest thing is to consider requirements.txt to be the 'developer route' and leave the pyproject.toml pointing to the last tagged release, via pypi?