Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add a `metadata` field to kernelspecs. #274
Currently, the only way for a kernel to offer additional information about its
This adds support for a new kernelspec dict field,
Currently, the only way for a kernel to offer additional information about its capabilities is to encode information into the kernel name or display name; this information can be useful to clients, especially for things like filtering a list of kernels. This adds support for a new kernelspec dict field, `metadata`. This allows kernels to add additional information, which clients can then consume as needed.
Ah, @takluyver, this does seem like it'd be exactly the information you'd want to return as kernel info in
That actually brings up an interesting parallel I hadn't realized at first -- internally at Google, we don't use conda/virtualenv/etc at all, but the "different libraries" I alluded to in #273 are a really close analogue to different virtualenvs or conda environments, where each has a fixed set of libraries installed (possibly with particular build configurations for C++ libraries, that sort of thing). So I suspect we're actually solving roughly the same problem -- meaning I can hopefully bootstrap off some of what you're doing in #261.