You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently give kernel types relatively simple display names like "Python 3". The ability to have multiple independent kernel providers makes it more likely that multiple kernel types will have the same name, which is confusing for users.
I see two options for how we deal with this:
Have interfaces listing kernels show the kernel type ID alongside the kernel name, e.g. "Python 3 (spec/python3)".
Encourage kernel providers to provide more detailed display names which are more likely to be unique, e.g. "Python 3 (from kernelspec)" or "Python 3 (using server's Python)".
I favour option 1: while it might be a bit more intimidating for new users who only have one or two kernels available, it easily provides an unambiguous way to identify each kernel type. The identifiers will also probably be visible in other contexts (e.g. command line options). Finally, referring to things (variables, files, servers, etc.) by precise identifiers rather than vague descriptions is a key general concept which programmers have to be used to.
The text was updated successfully, but these errors were encountered:
We currently give kernel types relatively simple display names like "Python 3". The ability to have multiple independent kernel providers makes it more likely that multiple kernel types will have the same name, which is confusing for users.
I see two options for how we deal with this:
I favour option 1: while it might be a bit more intimidating for new users who only have one or two kernels available, it easily provides an unambiguous way to identify each kernel type. The identifiers will also probably be visible in other contexts (e.g. command line options). Finally, referring to things (variables, files, servers, etc.) by precise identifiers rather than vague descriptions is a key general concept which programmers have to be used to.
The text was updated successfully, but these errors were encountered: