Installing with pip no longer works due to removal of package_index from setuptools

[kachulis]

setuptools.package_index was recently removed from setuptools. So installing with pip now hits an error ModuleNotFoundError: No module named 'setuptools.package_index'.

This can be worked around by manually installing an older version of setuptools (anything older than 80 seems to work), and then forcing pip to use the local version with --no-build-isolation.

However, it also seems worth updating fiss setup.py to no longer use setuptools.package_index.

[nsoranzo]

Additionally, having firecloud wheels on PyPI would completely avoid this problem. See https://pythonwheels.com/ for a list of advantages of providing wheels.

[ksuderman]

It looks like setuptools has rolled back the breaking changes in 80.3.0 so this isn't as urgent as it once was, but it is definitely something to keep an eye on as package_index will be removed eventually.

[nsoranzo]

It looks like setuptools has rolled back the breaking changes in 80.3.0 so this isn't as urgent as it once was, but it is definitely something to keep an eye on as package_index will be removed eventually.

@ksuderman I don't think they have, I don't see that mentioned in https://setuptools.pypa.io/en/stable/history.html . You are probably not encountering the issue in Galaxy only because I've published a wheel on our https://wheels.galaxyproject.org/ as mentioned in galaxyproject/galaxy#20283 (comment)

[ksuderman]

Right... I didn't notice wheels.galaxyproject.org is added as an extra-index-url in Galaxy...

[zhwshen]

I ran into now this issue with different setuptools (v65.5.0 and v80.9.0) on my MacOS. I tried both pip install firecloud and python setup.py install. But both still gave me ModuleNotFoundError: No module named 'setuptools.package_index'. I want to keep firecloud installation as a part of the requirement.txt for a package, so what is the recommended fix for this issue? It used to work OK not long ago. Thank you!

[bwalsh]

Getting same error trying to install terra-notebook-utils
DataBiosphere/terra-notebook-utils#419

[nsoranzo]

#193 would workaround the issue.