Interactive mode in debugging fails as you try to use "imports" or just use "print 'hello world'". This seems to be a error that only exists until python 3.0 ?
Example code:
'''
Created on 14. jun. 2016
'''
import time
Debugger output:
pydev debugger: starting (pid: 6988)
>>> time.sleep(4)
File "<stdin>", line 1
time.sleep(4)
^
SyntaxError: invalid syntax
>>>
This error has been found on eclipse mars 2.2 with newest pydev from the repostory (5.0.0).
With the same eclipse 4.5.2 (Mars) and LiClipse with 5.0.0 or 4.5.5 Java 1.7.0.80 in windows the error persists. In Lubuntu with the LiClipse it works with out fail.
So the error seems to only occur in windows.
The invalid syntax is pointing to the end of the line in time.sleep(2).
Instead of using -i, you should use the actual interactive console: http://www.pydev.org/manual_adv_interactive_console.html.
I think you're having issues with \r\n there, which is why it works on Linux -- it's possible that changing preferences > general > workspace > new text file line delimiter will actually make it work so that it uses \n, but this mode of execution in PyDev is not really supported, if you want an interactive console you should use http://www.pydev.org/manual_adv_interactive_console.html.
Related
I recently set up jdtls using Mason and it requires Java 17 while I still want Java11 as my default version. How can I point neovim to use the specific Java version?
On my set up, I use sdkman to manage my java version. On terminal I can use:
sdk use java 17.0.5-amzn
to change from Java 11 to Java 17. I've attempted to use Neovim cmd to execute this but it could not find sdk for some reason. On NeoVim:
:!sdk use java 17.0.5-amzn
Or even within the file:
vim.cmd([[!sdk use java 17.0.5-amzn]])
This will return me
/bin/bash: line 1: sdk: command not found
command not found in Neovim, while usable in the terminal
I also tried:
:call system("sdk use java 17.0.5-amzn")
:checkhealth
will still return me Java11
Any thoughts on how to achieve this? I have been scratching my head all day...
After installing code-oss on Manjaro Linux along with the Jupyter extension for code and jupyter-notebooks itself, the extension seems to error when I try to do anything Jupyter related inside code. If I try to create a new notebook from the command pallete, it pops up a dialog saying this:
Command 'Jupyter: Create New Jupyter Notebook' resulted in an error (command 'jupyter.createnewnotebook' not found)
Code then tells me that the extension activation failed and to open the chrome developer console for more information. This is what the chrome console then says:
extension activation failed Error: Extension 'ms-toolsai.jupyter' CANNOT use API proposal: notebookEditor. Its package.json#enabledApiProposals-property declares: but NOT notebookEditor. The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-toolsai.jupyter
Initial Pop-up error
Chrome Console error
You can solve that problem by inserting"enable-proposed-api": ["ms-toolsai.jupyter"] in the start settings of vs code. So press CTRL+ALT+P -> "Preference: Configure Runtime Arguments" then insert the upper line. After that restart vscode.
Had the same problem and found out this is happening because of the open source version of code - OSS. It does not have the proper config in the product.json.
The accepted solution to add to Runtime Arguments unfortunately didn't work on Arch.
Easiest solution for me was to install code-features from AUR.
You can find more info on arch wiki site
Or directly on microsoft docs regarding oss code issues.
The solution to add "enable-proposed-api": ["ms-toolsai.jupyter"] to the runtime of vscode didn't work for me on Arch linux. But when I started vscode from the command line using the argument "--enable-proposed-api ms-toolsai.jupyter" the problem was solved. So I created a custom desktop launcher for this:
Fist, copy the desktop launcher to your applications folder
$ cp /usr/share/applications/code-oss.desktop ~/.local/share/applications/.
Then edit the new file:
$ nano ~/.local/share/applications/code-oss.desktop
Now add "--enable-proposed-api ms-toolsai.jupyter" to both of the Exec lines like so:
[Desktop Entry]
Name=Code - OSS
Comment=Code Editing. Redefined.
GenericName=Text Editor
Exec=/usr/bin/code-oss --enable-proposed-api ms-toolsai.jupyter --unity-launch %F
Icon=com.visualstudio.code.oss
Type=Application
StartupNotify=false
StartupWMClass=Code
Categories=TextEditor;Development;IDE;
MimeType=text/plain;application/x-code-oss-workspace;
Actions=new-empty-window;
Keywords=vscode;
[Desktop Action new-empty-window]
Name=New Empty Window
Exec=/usr/bin/code-oss --enable-proposed-api ms-toolsai.jupyter --new-window %F
Icon=com.visualstudio.code.oss
I restarted my computer and the problem was solved.
It seems that everything cygwin-related configured and works fine in my Eclipse project, for example Eclipse is able to invoke 'make' or 'gcc', and can even run the compiled binary and show the output in the Eclipse console window.
However, when I try to debug my binary within Eclipse, I get the following error:
Error in final launch sequence:
Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program exited with code 0xc0000135.
Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program exited with code 0xc0000135.
During startup program exited with code 0xc0000135.
I do able to launch gdb from my Cygwin console, so it is installed correctly (I assume). But why it fails when I try to use it from Eclipse?
For my case, as you say, it turns out that adding the Cygwin bin folder to the PATH variable solves this problem.
I use Eclipse 2020-06 and Cygwin 64bit on Win7 64bit. And installing Cygwin doesn't change the PATH variable currently.
But it is also confused to me that "build" and "run" work fine in Eclipse whithout the Cygwin bin in PATH.
I am new to Python, so I have likely done something obviously wrong, though despite my best efforts I cannot figure out what.
I am running windows 7 64bit.
I only have Python 3.5 (32 bit) installed.
I updated pip to the latest version succesfully and used it to install pySerial. I am working in eclipse oxygen with PyDev installed. My run configuration does show the appropriate path (as far as I can tell):
run configuration in eclipse/PyDev
I have confirmed pySerial is installed by doing the following in python interpreter:
>>>help()
>>>modules
serial shows up in the list of modules.
also:
>>> import serial; print(serial.__file__)
C:\Python35\lib\site-packages\serial\__init__.py
Additionally, trying to use serial in the terminal works fine, as below:
>>> import serial
>>> s=serial.Serial("COM4")
>>> s
Serial<id=0x383b750, open=True>(port='COM4', baudrate=9600, bytesize=8, parity='N', stop
bits=1, timeout=None, xonxoff=False, rtscts=False, dsrdtr=False)
However, when I try to run the following code as a file:
import serial
print ("Test Script")
I get the following error:
Traceback (most recent call last):
File "C:\Users\H260643\Desktop\Projects\EclipseWorkspace\CMP_Thous_Hr\Base.py", line 1, in <module>
import serial
ImportError: No module named 'serial'
For what it's worth, the eclispe editor window has also flagged that line saying it is an "unresolved import: serial"
Right after posting this I realized that the install path for python/pySerial did not match what was in my eclispe/PyDev run configuration. I corrected my run configuration and all is well.
My problem is that when I try to start debuggin in DDT in Eclipse (Kepler) an error shows up:
Error in final launch sequence
Failed to execute MI command:
-gdb-set auto-solib-add on
Error message from debugger back end:
No symbol table is loaded.
Use the "file" command.
No symbol table is loaded.
Use the "file" command.
I've compiled the application with -gc and -g flag but it didn't help.
I'm using original DMD compiler.
Sounds like you are working on Windows, DMD has no GDB support there yet. You can either use windbg from the command line or use the Visual Studio plugin, which converts the debug info after compiling.
The issue that I had is that the compiler (DMD) is not working with GDB under Windows. If somebody wants to use DDT with debugging support, he needs to use GDC compiler.
This actually is mentioned in the "Debugging" page:
http://wiki.dlang.org/Debugging