-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exio3 parser permission error #35
Comments
Hi, I can not reproduce the bug. Are you using the latest publicly available exiobase version: you should have a exio34.ini file in the extracted directory. |
Yes I have the exio34.ini file in the extracted directory
…On Wed, 28 Nov 2018 at 08:44, Konstantin Stadler ***@***.***> wrote:
Hi, I can not reproduce the bug. Are you using the latest publicly
available exiobase version: you should have a exio34.ini file in the
extracted directory.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXKRxFLALIdku7I3tlyJitJhBBSWMBJhks5uzpM4gaJpZM4YgG-3>
.
|
Hi, can you do
and send me the output. |
Hi,
sorry for the late reply.
print("Python :{}, pandas: {}, pymrio: {}".format(sys.version_info,
pd.__version__, pymrio.__version__))
Python :sys.version_info(major=3, minor=6, micro=6, releaselevel='final',
serial=0), pandas: 0.23.4, pymrio: 0.2.2
…On Thu, 29 Nov 2018 at 11:33, Konstantin Stadler ***@***.***> wrote:
Hi,
can you do
`
import pymrio
import sys
print("Python :{}, pandas: {}, pymrio: {}".format(sys.version_info,
pymrio.pd.*version*, pymrio.*version*))
`
and send me the output.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXKRxEUYz1jb-bv0NWgePLduBb6H1xALks5u0AxBgaJpZM4YgG-3>
.
|
There is your problem: you are far behind the current release. Current pymrio version: 0.3.8 - you use 0.2.2. Run pip install pymrio --upgrade This should solve your problem. Anyway, please let me know if it worked. |
Yes it works. Thought I had already installed the latest version of pymrio.
Sorry for the dumb mistake and thank you.
Best regards
…On Wed, 5 Dec 2018 at 16:51, Konstantin Stadler ***@***.***> wrote:
There is your problem: you are far behind the current release. Current
pymrio version: 0.3.8 - you use 0.2.2. Run
pip install pymrio --upgrade
This should solve your problem. Anyway, please let me know if it worked.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXKRxBSvD0IElT6mowJsX7o5Vkfyy9UUks5u2D_FgaJpZM4YgG-3>
.
|
No problem. Happy to help! |
Hi,
I am trying to use the parser of exiobase3 and I get a permission error. It seems that the parser only accepts zip files? Yet, when I use the zip file directly downloaded from exiobase website it tells me KeyError: "There is no item named 'mrIot3.0.txt' in the archive", and when i use the unzipped file i get the following error:
io = pymrio.parse_exiobase3('C://Users/Maxime/Desktop/Thesis/Bdd/IOT_2011_pxp/')
PermissionError Traceback (most recent call last)
in ()
----> 1 io = pymrio.parse_exiobase3('C://Users/Maxime/Desktop/Thesis/Bdd/IOT_2011_pxp/')
C://Users/Maxime/Desktop/Thesis/Modules_Python/pymrio-master\pymrio\tools\ioparser.py in parse_exiobase3(zip_file, path_in_zip, version, iosystem, year, charact)
498 # read the data into a dicts as pandas.DataFrame
499 logging.info('Read exiobase3 from {}'.format(zip_file))
--> 500 zip_file = zipfile.ZipFile(zip_file)
501
502 core_data = {exio_table: pd.read_table(
C:\Users\Maxime\Anaconda3\lib\zipfile.py in init(self, file, mode, compression, allowZip64)
1088 while True:
1089 try:
-> 1090 self.fp = io.open(file, filemode)
1091 except OSError:
1092 if filemode in modeDict:
PermissionError: [Errno 13] Permission denied: 'C:\Users\Maxime\Desktop\Thesis\Bdd\IOT_2011_pxp'
The text was updated successfully, but these errors were encountered: