oemof.tabular installation process stops on three different Macs with different errors about oemof-tabular

[jnnr]

Hi Olav, thanks for reporting! I am afraid I do not have the answer ready. I also do not have a mac to reproduce.

But I suggest that you try to follow the AttributeError: module ‚import lib_metadata‘ has not attribute ‚MetadataPathFinder‘. I found some forum entries on that topic.

Please keep us updated on your progress!

[OHO53]

Hi jnnr,

it turned out to be a problem with the specific version of numpy. After forcing numpy1.17.0 into the installed software environment (virtual python3.6 environment under anaconda) the installation worked on the iMac27. Nevertheless, running a program (base_NDE_sde.py originally developed by Maruf for oemof.tabular) using oemof.tabular then produced an error while importing enum from pyutilib. I get the error message

'Import Error: pyutilib.enum has been removed. Python 3 now has an enum implementation in the standard library that supersedes this library.'

The program did not run after all.

I have seen that gplssm has run into a similar error using oemof.solph with wind node-abw, but there didn't seem to be a satisfactory answer.
Could anyone give me the relevant version numbers of the packages to be imported to run oemof.tabular smoothly? Right now we seem to be running into a number of problems due to newer versions of the imported packages, which are in conflict with some of the programming in oemof.tabular. Would be great if these essentials could be specified for the installation routine!
Thanks for any help on this problem.

Olav

[OHO53]

The problem with the enum module was solved by deleting the existing pyomo version and and installing pyomo5.7 for the virtual environment. Now the program imports all necessary programs. So I'm down to some internal python problems, which should, hopefully, be solved within the next few days.

[jnnr]

Thanks again for reporting, @OHO53!
We could use poetry in the future which provides a poetry.lock file specifying the versions of all used packages.
Please let us know if you encounter more issues.

[OHO53]

After settling the issues with pyomo5.7 a side effect was that this does not satisfy oemof 0.3.2, which requires promo < 5.7. Nevertheless, oemof.solph 0.4.3 requires promo >= 5.7. Thus, there may still be a conflict between the different specifications.