Thanks, Tuan -- I'll give that another try!
I was pretty sure I'd tried the above, but hit a problem with vscode
complaining about something being binary when it wasn't expected. Perhaps
this is to do with debugging on Windows, where the 'nameko` command is a
binary executable rather than a script shebang'd to point to python.exe.
(I'm trying to hit that perfect vscode configuration where I can hit F5 on
a service.py and it'll run under the nameko shell on Windows, Linux and
macOS).