As seen on the screenshot below  This, imo, can be fixed, providing virtual-env-like shell with 'deactivate' command