As pointed out in issue #42, when @ruairidhcumming tied to load exiobase2, an error message was raised saying that the population.txt file was not found
@konstantinstadler suggested that it may have to do with the hard-coded relative path at line 656 of tools/ioparser.py
Main changes:
fixes OS-specific hard-coded relative path in parse_exiobase2() for population.txt, as pointed out above
Issues:
Fixes only partially the problem brought up by issue #42, by making the relative path OS-independent using os.path.join()
However, it can be seen that:
the problem is solved when pymrio is installed from a github clone
the problem is not solved when installed from pypi using pip
The reason for this is that the pip installation does not seem to include the following diretories and data: exio20
Indeed, when checking the content from my github cloned repo:
Clearly, exio20 is not included in the pip installation, which means users using pip will have the same issue even after this PR.
Opening a separate issue to deal with this, which should be done both in the setup.py and in a MANIFEST.in from what I know.
Motivations:
Main changes:
parse_exiobase2()
for population.txt, as pointed out aboveIssues:
Indeed, when checking the content from my github cloned repo:
When checking from the pip-installed version:
Clearly, exio20 is not included in the pip installation, which means users using pip will have the same issue even after this PR. Opening a separate issue to deal with this, which should be done both in the setup.py and in a MANIFEST.in from what I know.