-
Notifications
You must be signed in to change notification settings - Fork 285
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
make resource 에서 오류 발생 #5
Comments
I got similar error but with no syntax error Traceback (most recent call last): |
@Kimdoun f-string 포맷에서 invalid syntax 오류가 나오는 것을 보면 python 버전이 3.6 미만인 것 같습니다. |
@Ella77 You have to install pytorch by running |
I did but I didn't assure installments are done. (for someone experiencing same error) Because there is my specific problem while installing. with --user option I could install |
String literals in Python are a relatively new feature, and unless you have full control over the stack involved it seems like a rather risky thing to use - in particular it doesn't seem like a great fit for a open source library. Considering that a significant chunk of the academic community is still stuck on Python 2, would be nice to fix. This doesn't seem like a complex issue to fix, unless significant parts of the resource build pipeline has unicode-isms. (expecting str types to be unicode, rather than bytestring) Is that the case? |
This fixes the Py3.6-isms, but will not fix cases where a string is expected to be unicode. I haven't checked if that is the case, but judging from the nature of the project the likelihood of a follow-up patch to fix that seems pretty high.
This fixes the Py3.6-isms, but will not fix cases where a string is expected to be unicode. I haven't checked if that is the case, but judging from the nature of the project the likelihood of a follow-up patch to fix that seems pretty high.
오류
make all 까지 100% 진행이 다 되고
bin/khaiii 생성되고
build/khaiii/share/khaiii 폴더 밑에는 아무것도 없습니다.
파이썬 버전과 requirement에 버전은 전부 확인했는데 이상없었습니다.
환경은 linux, docker container 내부에서 git clone하여 실행시켰습니다.
The text was updated successfully, but these errors were encountered: