- Notifications
You must be signed in to change notification settings - Fork379
Path resolver API#1331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Path resolver API#1331
Uh oh!
There was an error while loading.Please reload this page.
Conversation
krassowski commentedJan 31, 2024
@meeseeksdev tag enhancement |
Awww, sorry krassowski you do not seem to be allowed to do that, please ask a repository maintainer. |
krassowski commentedFeb 11, 2024
Can a repository maintainer add labels to my pull requests or configure lumberbot to make it usable? It helps to see what is the CI status and reduces number of distracting spam emails about failure status. |
blink1073 commentedFeb 11, 2024
I'm afk for the next few days but would merge such a PR. 😃 |
krassowski commentedMar 25, 2024
Marking this as ready-for review because:
However, if the decision is to go withjupyter/jupyter_client#1006 and close this PR (along withjupyter/jupyter_client#1005) I would totally understand this. |
krassowski commentedApr 25, 2024
Another use case for this API isjupyterlab/jupyterlab#16235 - we currently cannot reliably reconcile the files returned by the debugger with the file system. |
krassowski commentedDec 10, 2025
I updatedjupyter/jupyter_client#1005 and it is back to green now. |
krassowski commentedDec 11, 2025
jupyter/jupyter_client#1005 was merged but I think we still need to wait for a release. |
Uh oh!
There was an error while loading.Please reload this page.
This patch demonstrates the scaffold of the new path resolver API endpoint proposed in#1280.
This depends on a sibling PRjupyter/jupyter_client#1005
Questions:
self.kernel_managerorself.multi_kernel_manager? (these are not well documented in code)In future we could include an entry point (e.g. traitlet) to define additional scopes (e.g. from remote file systems), but this is out of scope for this PR which focuses on distinguishing between a path from kernel and server.