Python debugger hangs after running 'start without debugging' until reopen of VSCode

[ZacKeskin]

Environment data

VS Code version: 1.18.1
Python Extension version: 0.8.0
Python Version: 3.6.1 (Anaconda)
OS and version: Mac OSX Sierra 10.12.5

Actual behavior

After running 'Start Without Debugging', the code is run through without issues, once, and then the debugger panel appears to be in some kind of wait phase or loop (blue loading bar travelling from left to right)? Running neither 'Start Debugging' nor 'Stop Debugging' at this point appears to do anything, with nothing visible in Call Stack. The only way to reset this appears to be to quit the application.

This has been occurring for a month or so; updating VSCode, and uninstalling/reinstalling Python extension has not helped.

Expected behaviour

Used to be able to press stop-debugging, and then could start without debugging again.

Steps to reproduce:

• With VSCode and Python extension installed, run 'Start Without Debugging'
• Try to end the session and/or run 'Start Without Debugging' another time.

Logs

n/a

Output from Console window (Help->Developer Tools menu)
n/a

Example of hanging/loading behaviour

Default load.json file provided by Python extension.

Apologies if this is user error and if I have missed anything obvious.

Thanks!

[DonJayamanne]

Duplicate of #235
We're planning on releasing a new version with the fixes some time today/tomorrow.

[Zac-Keskin]

Thanks! Appears to be fixed but I sometimes seem to get a new problem now when doing the same as above.

I receive the warning:

sh: sysctl: command not found

followed by ImportErrors for some modules which are definitely installed (e.g. keras, statsmodels, sklearn) although others appear to be found fine (e.g. pandas, numpy, math).

I can't reproduce this error in all workspaces (e.g. a project wherein keras was already being used appears to work fine, and a newly-created workspace in also VSCode seems to be fine), but within the workspaces presenting this problem, even when adding a new file, the error is still seen.

Any ideas?