Open dt-woods opened 2 years ago
I think we have found that pip has trouble handling github based dependencies for a specific version so we (typically) no longer specify versions for other packages within the tool ecosystem. I believe this needs to be updated within elci setup
I found another resolution issue with StEwI 0.9.5 (requires numpy 1.19.3) and esupy 0.2.0 (requires numpy >1.20), which causes havoc with pandas, which doesn't work seamlessly with these variants.
@dt-woods please update to use StEWI v1.05 - that will align them https://github.com/USEPA/standardizedinventories/releases/tag/v1.0.5
FYI @bl-young
FYI: the latest versions of
lciafmt
(v1.0.3) andelectricitylci
(v.1.0.1) have a conflicting (and impossible to resolve using setup.py and requirements.txt) dependencies onfedelemflowlist
. This is likely caused by severe numbering in the requirements of these individual packages. Typically bug fixes (i.e., patch numbers from Backus-Naur Form Grammar as recommended by GitHub) don't cause backwards compatibility issues and, as such, probably need not be explicitly defined as a requirement; after all, it shouldn't break API functionality. Unfortunately, this breaks software installations that depend on these packages and the only solution (that I know of) is to manually install these packages one at a time allowing old dependencies to be uninstalled and new dependencies to be installed. It is my recommendation that ranges be used or specific patch fixes be removed from software release requirements in future releases.To reproduce the error, create a new Python virtual environment and create a requirements.txt file with:
The following error is encountered (using Python 3.9.10).