We Keep Coding

How to Disable Kite Copilot Feature?

I recently installed Kite for Spyder 4. I think I wanted to give it a try for several weeks and see how it performs.
One feature called Kite-copilot annoys me, it pops up whenever I opened spyder. I don't really use that feature much since it is in the new window (it would cover my workspace if it is always on top, and it would be covered by spyder if it didn't).
So is there a way to disable this particular feature? I know I can just close it right away whenever it pops out, but it is kinda annoying that I always need to close it first whenever I opened spyder.

On MacBook switch off kite for current session: at the top right of the screen (top menu bar where your wifi shows etc) locate the kite icon. Right click on it and select 'quit kite'. You will see in Spyder at the bottom (just below Console) the Kite status should switch to 'Kite: not running'.

Pycharm: How to focus on Editor when hit a debug point

I am using a mac, with Pycharm version 2018.2.4 Community version.
When I run a debugging session using the debugger and hit a debug point, I have to click on my editor using my mouse to be able to type code on the editor. If I don't do this and hit my keyboard directly, Mac will complain with some "bing" sound, signaling the keyboard input is not valid to any application (my opinion).
How to make my Pycharm auto focus on the editor when hitting the debug point? Or at least focus on the debugger so that I can hit ESC to focus on the editor?
I have selected "Focus application on breakpoint" in the setting.

This is how it should work:
In Preferences, type Focus application on breakpoint into the search bar and be sure it is toggled on.
Apply that setting and exit Preferences.
In your debugger, when you hit a breakpoint, hit the escape key, and your cursor should be blinking in your editor.
For me, I had to disable the setting, apply, re-enable the setting and re-apply once more.
It now behaves as stated above.

There is a bug reported on PyCharm for the same. Here is the link to the issue. The bug is reported for version 2018.2 and still not fixed.

Python freezes when configuring IDLE

So, recently I was using the Python theme function for the IDLE program itself. I downloaded three themes and built my own one, which is selected now. The problem is, I forgot to set colours for the blinker and highlighting, which is hugely problematic. When I went to see if I could change back to the default setting, Python IDLE simply froze up when I selected 'Configure IDLE' under options. I can still scroll through the file, attempt to close the window and minimise it etc, but it has just frozen up. I can't close it or continue working with the file. I've removed Python and then reinstalled it but that hasn't worked, should I just manually delete the themes and force IDLE to use the original one, or is there a way to fix this?
I am running Python 2.7 on Windows 8.1.
Thanks

Turns out one way is manually deleting the faulty theme. This allows the Configure IDLE menu to open. Whoops.

How do I not allow pygame to change my screen resolution in Linux?

I've recently written a shell script which boots my Windows Python application with wine:
#!/bin/sh
wine data/Python/x86/python.exe loader.py 'x86'
While the program is running, everything works as expected. The problem is, when the SDL window is displayed, my second monitor is disabled, and the orientation of my primary monitor changes. The resolution of my primary monitor stays the same. My question is, what can I do to disable these changes?
Installing a Linux Python interpreter is out of the question, because the solution:
1: needs to be portable
2: would currently oversize download
EDIT:
some extra info, I just recently ran it with a terminal and got:
fixme:win:EnumDisplayDevicesW ((null),0,0x42f3ec,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x42f46c,0x00000000), stub!
fixme:wgl:X11DRV_wglChoosePixelFormatARB unused pfAttribFList
not sure if this solves anything though

If you run winecfg you can set it to run all applications in a window. From http://ubuntuforums.org/showthread.php?t=693292
Applications --> Wine --> Configure Wine or just run winecfg from the
terminal
Click on the Graphics tab Check the "Emulate Virtual Desktop" box And
enter in the virtual Desktop size (like 800x600 or something).
It sounds like your pygame application is setting a resolution and switching to fullscreen. If you could disable fullscreen in the pygame app, this would probably also work.

Well, I've used it long enough to verify this was the case.
I'd not even used linux for a month before posting this question.
The issue happened because of Wine version 1.6 incompatibilities.
The solution is to update Wine.

PyCharm does not highlight errors

I have a problem with PyCharm v2.7.
it does not show me errors.
I have configured it to show them as here
but nothing.
here a screenshot of what I see (no error displayed)
if I run code analysis it shows the errors marked as INVALID in the window but it does not highlight the code.
any idea?

I had this issue recently on PyCharm 2020.3.3 Community Edition.
What I've found is in the top right corner of the editor there is a Reader Mode button.
If you click it you turn the Reader Mode off and then you can see your errors.
You can re-enable it by clicking the book icon

I found. i've enabled by chance the "power safe mode" that avoid error checking. it can be re-enabled by clicking on the little man on bottom right corner.

In my case, I had some ticks disabled in the Python Inspections menu in Settings > Editor > Inspections > Python. I have ticked everything and applied, and now it is working.
I don't really understand why this happened as the problem arose from one day to another. I had even re-installed the whole PyCharm, trying older versions, and deleted the .pycharm configuration folder from home.

I had the same issue with PyCharm Community Edition, v.2016.3.2. To fix,
go to Preferences... from the PyCharm menu, and open Editor/Colors & Fonts/General
Now go to Errors and Warnings/Error under your current schema.
I also had to set my Project Interpreter under Preferences/Project:<name>/Project Interpreter.
See screenshot.

None of the previous answers worked for me when I ran into this issue, but I was able to fix it by doing a hard reset on my PyCharm settings:
From the main menu, select File | Manage IDE Settings | Restore Default Settings.
You will lose all your custom settings this way of course, but this was the only thing that worked for me.

I have tried many things, but only Invalidate Caches did the trick, after that I could hover the green arrow (top right side) and change Highlight to All Problems

I needed to "Add content root" under "Project Structure" in Preferences. I had no content root.

Nothing of this worked for me.
My problem was a single warning: "unreachable code" which blocked all errors from being highlighted.
I removed this line of code (+ the warning) and all errors showed up again.

For me, this problem was a symptom of having created the file in the wrong place without realising. Before taking any drastic actions, check your project structure