pycharm completions are broken
See original GitHub issueGenerating this file with protoc --python_out=. --mypy_out=. tetration_network_policy.proto
on python 3.7. Python 3.6 tested with same results.
The resulting file is full of Unresolved reference 'TetrationNetworkPolicyProto'
errors and auto-completions does not work. You can check the screenshot here:
When I simply delete all the TetrationNetworkPolicyProto.
occurrences in the file, tada! All errors are gone and completions throughout the project work great. I’m not versed enough with the mechanics of python typing yet so I’ve had no insights for where the problem could be coming from.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Is Pycharm completely broken
Now, it seems to me completely broken in its basic functions. The IDE seems to be poorly tested, abandoned, with no plan to...
Read more >Code completion is broken / unreadable suggestions
I have a very strange problem with code completion for month now. The code completion suggestions are just mixed up letters.
Read more >Code completion | PyCharm Documentation - JetBrains
Techniques to accelerate the editing process in PyCharm using code completion (basic completion, smart completion based on type, ...
Read more >After update to 2022.2 code completion broken. There are no ...
Hi. The big scala project. On 2022.1 all works fine. After update => subj. I did Invalidate caches..(with all checkboxes), Repair IDE, reopen...
Read more >Code completion stopped working after update to PyCharm ...
I'm currently using PyCharm Professional Edition on Ubuntu 20.04 LTS. My PyCharm have just updated via Snap from 2021.2. 0 version to 2021.2....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for the report! Looks like a real bug.
I believe that
mypy-protobuf
has a bug where if you have a capitalized package name (likeTetrationNetworkPolicyProto
or a lowercase message name, thenmypy-protobuf
generates incorrect code.This is due to a rather unfortunate usage of
isUpper
inprotoc-gen-mypy
to determine the relative path.We never came across this because we were primarily using this in go and python which have different standard casing models.
Working on a fix! Appreciate the report.
Pulled 1.9 and running smoothly with lowercased messages, thanks again!