Closed tinmarino closed 4 years ago
Sorry, there is a conflict now after I merged the other PR in. Can you rebase? Otherwise I think we can also merge this in now.
Sure, give me 5 min. This is the problem of Minimum viable change method (of witch I am not really fan). Are you actually ?
Tested and pushed.
The only real conflict was the __init__
parameters. But git got trouble because some function were added just close to some changes.
Thanks, merged now. I guess sometimes Git (or diff/patching) could be more clever, like in such a case, although it can be tricky, and sometimes not so straightforward how it actually should resolve.
A pleasure (not to say an honor), to have collaborated. Have a nice Sunday.
Fix part2 of #2: The connection file are written in the current directory which could be annoying. If jupyter is present, it can give a default data path.
You can see that the ls (top right) do not show any
kernel-*.json
and the--existing
advice (bottom left) is shortened to the only required pid (proof right). Also, you can see print as no return because it is another PR to follow the Minimum Viable Change philosophy