qwerty_ww's profile - activity

I'm so-to-say forced to use Anaconda ans hve that no insalled in my Mac. However, the environments drop down does only show crap. Tht is some none-existing brew-installtions (usr/local/Cellar//python@3.9/3.9.1_1/bi…) . Not sure what's going on here.

Reinstallation solved the issue. It was also an upgrade of the WW version (to 9.1.2). So this will be left one of the IT

Looks like re-installation solved this issue. Need to verify tomorrow. Strange thoug

anaconda not shown in Environments I'm so-to-say forced to use Anaconda ans hve that no insalled in my Mac. However, the

I switched back to V7 and there it worked. So it must be related to the V9 upgrade.

Connecting to host id ... failed. Probing the remote agent timed out. I recently installed V9 on my Intel MBP. Now I tri

Turned out that the Watch was the culprit. I usually don't need it and it's not in my focus. Once I removed everyting th

Turned out thath the Watch was the culprit. I usually don't need it and it's not in my focus. Once I removed everyting t

Turned out thath the Watch was the culprit. I usually don't need it and it's not in my focus. One I removed everyting th

I'm working on an Intel MBP under OSX 13.1 (22C65), WingPro 7.2.2.13 (rev b4c7d93c92a9).

Now I'm running in an issue that the debugger sleeps for a couple of seconds after each step. I had this issue in the past but somehow it always went way after either restarting Wing or the Mac (I don't remember exactly). But now this issue persists. Right yesterday I could debug the very same file without issue but today it gets me pulling my hairs. What could that be?

Debugger slow I'm working on an Intel MBP under OSX 13.1 (22C65), WingPro 7.2.2.13 (rev b4c7d93c92a9). Now I'm running

Debugger slow I'm working on an Intel MBP under OSX 13.1 (22C65), WingPro 7.2.2.13 (rev b4c7d93c92a9). Now I'm running

I'm using WW with a remote debug session. On the remote machine my .bashrc includes a setting of PYTHONPATH and it works well when running my script via ssh. However, when running through WW debugger the variable is not set. I echoed sys.path and the path does not contain my addition. I also tried adding it via the Project settings in WW but to no avail. How would I do that?

P.S. My setting in the environment is like Environment But querying sys-path yields print("\n".join(sys.path)) /home/thomaskilian/3DP/Server /usr/bin/python3 /usr/lib/python37.zip /usr/lib/python3.7 /usr/lib/python3.7/lib-dynload /home/thomaskilian/.local/lib/python3.7/site-packages /usr/local/lib/python3.7/dist-packages /usr/lib/python3/dist-packages

right after the program start.

os.environ shows 'PYTHONPATH': '/usr/bin/python3'

Setting PYTHONPATH environment variable not working I'm using WW with a remote debug session. On the remote machine my .

I tried different ways. But setting it in the project properties did not seem to work. Just like the setting from .bashr

Setting PYTHONPATH environment variable not working I'm using WW with a remote debug session. On the remote machine my .

Learn something new each day :-)

I'm working on a Mac and want to open WW twice in order to debug a client and a server application side by side. I could use two different users but switching would be cumbersome (except I would use two machines). Someone told that you can have two instances of WW open under Windoze, but Mac OS does not seem to allow that.

Start two debug sessions I'm working on a Mac and want to open WW twice in order to debug a client and a server applicat

Setting PYTHONPATH environment variable not working I'm using WW with a remote debug session. On the remote machine my .

I do have W7 but the effect is still there. Killing the remote (by reboot or whatever) makes the debugger loose connecti

Yep, I found it. Always hard if you have so many option. Unfortunately, or luckily, the error did not re-occur after reb

I have set up a project to run a remote debugger on a Pi Zero. Basically it works. Basically. That is, the remote Python is started and the process runs. However, I rather soon get a timeout and that's it. But where can I increase that timeout?

Yep, I found it. Always har if you have so many option. Unfortunately, or luckily, the error did not re-occur after rebo

Increase timeout for remote debugging I have set up a project to run a remote debugger on a Pi Zero. Basically it works.

Ah, not to forget: I find editing such config files more handy than fiddling with any GUI trying to help me editing. May

I wonder where I could alter the setting for shift-space which in debug mode shows current stack data as overlay. Though this is a nice feature I always get in conflict when typing corrections during a debug session. Either I'd turn it off or assign it to an F-key.