Unresolved reference async/await in PyCharm
Sometimes in PyCharm 2017.1.4 with python3.6 async/await statements show as unresolved, although there aren't any errors and in next tab async/await not underlined as an error.
Restarting fix this issue.
How to fix that?
pycharm jetbrains
asked Jun 19 '17 at 20:43
comalex3comalex3
8311232
add a comment |
Sometimes in PyCharm 2017.1.4 with python3.6 async/await statements show as unresolved, although there aren't any errors and in next tab async/await not underlined as an error.
Restarting fix this issue.
How to fix that?
pycharm jetbrains
asked Jun 19 '17 at 20:43
comalex3comalex3
8311232
What's your question? If you think there's a problem with PyCharm, raise it with JetBrains.
– jonrsharpe
Jun 19 '17 at 20:44
This happened to me because of an unclosed statement above my function (missing close-paren)
– Curtis Mattoon
Jan 10 '18 at 17:11
add a comment |
Sometimes in PyCharm 2017.1.4 with python3.6 async/await statements show as unresolved, although there aren't any errors and in next tab async/await not underlined as an error.
Restarting fix this issue.
How to fix that?
pycharm jetbrains
asked Jun 19 '17 at 20:43
comalex3comalex3
8311232
Sometimes in PyCharm 2017.1.4 with python3.6 async/await statements show as unresolved, although there aren't any errors and in next tab async/await not underlined as an error.
Restarting fix this issue.
How to fix that?
pycharm jetbrains
pycharm jetbrains
asked Jun 19 '17 at 20:43
comalex3comalex3
8311232
asked Jun 19 '17 at 20:43
comalex3comalex3
8311232
edited Jun 19 '17 at 20:46
comalex3
asked Jun 19 '17 at 20:43
comalex3comalex3
8311232
asked Jun 19 '17 at 20:43
comalex3comalex3
8311232
asked Jun 19 '17 at 20:43
comalex3comalex3
8311232
8311232
What's your question? If you think there's a problem with PyCharm, raise it with JetBrains.
– jonrsharpe
Jun 19 '17 at 20:44
This happened to me because of an unclosed statement above my function (missing close-paren)
– Curtis Mattoon
Jan 10 '18 at 17:11
add a comment |
What's your question? If you think there's a problem with PyCharm, raise it with JetBrains.
– jonrsharpe
Jun 19 '17 at 20:44
This happened to me because of an unclosed statement above my function (missing close-paren)
– Curtis Mattoon
Jan 10 '18 at 17:11
What's your question? If you think there's a problem with PyCharm, raise it with JetBrains.
– jonrsharpe
Jun 19 '17 at 20:44
What's your question? If you think there's a problem with PyCharm, raise it with JetBrains.
– jonrsharpe
Jun 19 '17 at 20:44
This happened to me because of an unclosed statement above my function (missing close-paren)
– Curtis Mattoon
Jan 10 '18 at 17:11
This happened to me because of an unclosed statement above my function (missing close-paren)
– Curtis Mattoon
Jan 10 '18 at 17:11
add a comment |
2 Answers
2
active
oldest
votes
I just hit the same problem. It was because the project interpreter was set to python2.7, the await/async keys are new as of python3, and not backward compatible.
preferences>project>project-interpreter is where I could select the correction version.
answered Jun 28 '17 at 19:04
Luke ExtonLuke Exton
1,81721229
10
Project interpreter set python3.6. That is a bug of Pycharm
– comalex3
Jun 28 '17 at 22:08
Interpreter set to 2.5, encountered same bug, PyCharm 2017.3.3
– Jonathan Stray
Mar 1 '18 at 1:20
add a comment |
I encountered the same issue since I erroneously used the 'await' outside of an async method (Interpreter set to Python 3.6).
'await' is only valid in an 'async' method using Python 3.6. Pycharm correctly produces the error, but the message 'await unresolved' is not specific.
answered Nov 15 '18 at 1:10
giwynigiwyni
56256
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44639625%2funresolved-reference-async-await-in-pycharm%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I just hit the same problem. It was because the project interpreter was set to python2.7, the await/async keys are new as of python3, and not backward compatible.
preferences>project>project-interpreter is where I could select the correction version.
answered Jun 28 '17 at 19:04
Luke ExtonLuke Exton
1,81721229
10
Project interpreter set python3.6. That is a bug of Pycharm
– comalex3
Jun 28 '17 at 22:08
Interpreter set to 2.5, encountered same bug, PyCharm 2017.3.3
– Jonathan Stray
Mar 1 '18 at 1:20
add a comment |
I just hit the same problem. It was because the project interpreter was set to python2.7, the await/async keys are new as of python3, and not backward compatible.
preferences>project>project-interpreter is where I could select the correction version.
answered Jun 28 '17 at 19:04
Luke ExtonLuke Exton
1,81721229
10
Project interpreter set python3.6. That is a bug of Pycharm
– comalex3
Jun 28 '17 at 22:08
Interpreter set to 2.5, encountered same bug, PyCharm 2017.3.3
– Jonathan Stray
Mar 1 '18 at 1:20
add a comment |
I just hit the same problem. It was because the project interpreter was set to python2.7, the await/async keys are new as of python3, and not backward compatible.
preferences>project>project-interpreter is where I could select the correction version.
answered Jun 28 '17 at 19:04
Luke ExtonLuke Exton
1,81721229
I just hit the same problem. It was because the project interpreter was set to python2.7, the await/async keys are new as of python3, and not backward compatible.
preferences>project>project-interpreter is where I could select the correction version.
answered Jun 28 '17 at 19:04
Luke ExtonLuke Exton
1,81721229
answered Jun 28 '17 at 19:04
Luke ExtonLuke Exton
1,81721229
answered Jun 28 '17 at 19:04
Luke ExtonLuke Exton
1,81721229
answered Jun 28 '17 at 19:04
Luke ExtonLuke Exton
1,81721229
1,81721229
10
Project interpreter set python3.6. That is a bug of Pycharm
– comalex3
Jun 28 '17 at 22:08
Interpreter set to 2.5, encountered same bug, PyCharm 2017.3.3
– Jonathan Stray
Mar 1 '18 at 1:20
add a comment |
10
Project interpreter set python3.6. That is a bug of Pycharm
– comalex3
Jun 28 '17 at 22:08
Interpreter set to 2.5, encountered same bug, PyCharm 2017.3.3
– Jonathan Stray
Mar 1 '18 at 1:20
10
10
Project interpreter set python3.6. That is a bug of Pycharm
– comalex3
Jun 28 '17 at 22:08
Project interpreter set python3.6. That is a bug of Pycharm
– comalex3
Jun 28 '17 at 22:08
Interpreter set to 2.5, encountered same bug, PyCharm 2017.3.3
– Jonathan Stray
Mar 1 '18 at 1:20
Interpreter set to 2.5, encountered same bug, PyCharm 2017.3.3
– Jonathan Stray
Mar 1 '18 at 1:20
add a comment |
I encountered the same issue since I erroneously used the 'await' outside of an async method (Interpreter set to Python 3.6).
'await' is only valid in an 'async' method using Python 3.6. Pycharm correctly produces the error, but the message 'await unresolved' is not specific.
answered Nov 15 '18 at 1:10
giwynigiwyni
56256
add a comment |
I encountered the same issue since I erroneously used the 'await' outside of an async method (Interpreter set to Python 3.6).
'await' is only valid in an 'async' method using Python 3.6. Pycharm correctly produces the error, but the message 'await unresolved' is not specific.
answered Nov 15 '18 at 1:10
giwynigiwyni
56256
add a comment |
I encountered the same issue since I erroneously used the 'await' outside of an async method (Interpreter set to Python 3.6).
'await' is only valid in an 'async' method using Python 3.6. Pycharm correctly produces the error, but the message 'await unresolved' is not specific.
answered Nov 15 '18 at 1:10
giwynigiwyni
56256
I encountered the same issue since I erroneously used the 'await' outside of an async method (Interpreter set to Python 3.6).
'await' is only valid in an 'async' method using Python 3.6. Pycharm correctly produces the error, but the message 'await unresolved' is not specific.
answered Nov 15 '18 at 1:10
giwynigiwyni
56256
answered Nov 15 '18 at 1:10
giwynigiwyni
56256
answered Nov 15 '18 at 1:10
giwynigiwyni
56256
answered Nov 15 '18 at 1:10
giwynigiwyni
56256
56256
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44639625%2funresolved-reference-async-await-in-pycharm%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What's your question? If you think there's a problem with PyCharm, raise it with JetBrains.
– jonrsharpe
Jun 19 '17 at 20:44
This happened to me because of an unclosed statement above my function (missing close-paren)
– Curtis Mattoon
Jan 10 '18 at 17:11