-
Notifications
You must be signed in to change notification settings - Fork 70
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
ImportError: No module named config #7
Comments
Hi, the config file just defines some file paths. Actually, I didn't use the information in config file, you can delete this line. |
when I run main_mnli.py in SSE, I had the same error, "no module named config". After commenting out all "import config" from <mnli.py>,<torch_util.py> and main_mnli.py>, I have a nameError: global name 'config' is not defined in main_mnli.py. |
Sorry about the inconvenience, I just updated the config file: https://github.com/lanwuwei/SPM_toolkit/blob/master/SSE/config.py
Best,
Wuwei
From: funnytestingcase <notifications@github.com>
Reply-To: lanwuwei/SPM_toolkit <reply@reply.github.com>
Date: Thursday, January 7, 2021 at 8:12 AM
To: lanwuwei/SPM_toolkit <SPM_toolkit@noreply.github.com>
Cc: Wuwei Lan <lwwscc@gmail.com>, Comment <comment@noreply.github.com>
Subject: Re: [lanwuwei/SPM_toolkit] ImportError: No module named config (#7)
when I run main_mnli.py in SSE, I had the same error, "no module named config". After commenting out all "import config" from <mnli.py>,<torch_util.py> and main_mnli.py>, I have a nameError: global name 'config' is not defined in main_mnli.py.
I'm trying to create a config file, but I'm wondering if you can upload your <config.py> just for reference. Thank you in advance
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACDANXAJML4AKVDDHWBLAN3SYXMNJANCNFSM4FHZTFEA>.
|
I got this error while trying to run main_quora.py in SSE. Where can I find this file or how do I create it? Thanks!
The text was updated successfully, but these errors were encountered: