Nicholas Chisholm

If you don't mind calling `display` on each line you want shown, you get the desired result. ```org #+begin_src jupyter-python display("hello") display("world") #+end_src #+RESULTS: :RESULTS: : hello : world :END:...

Oh, I see - sorry if I stated the obvious then. It took me some time to figure out that you could call display a bunch of times to get...

> Should we open an issue for the kernel? The other two users are also on Linux, so it might be an issue with the Linux driver specifically. I can...

Aha: ```julia julia> import ArrayInterface as Arr julia> using StaticArrays julia> Base.IteratorSize(StaticArray{Tuple{2,3}}) Base.HasLength() julia> Base.IteratorSize(StaticArray{Tuple{2,3}, Arr.known_size(StaticArray{Tuple{2,3},

@chriselrod: As a temporary workaround, I type-pirated something like your code above into the (unpublished) package I am working on, and it did does fix the problem. Also: >> What...

> I'd prefer to return nothings and let the user decide how to handle this being unknown. They're free to throw if that is appropriate. Good point. > You could...

I am thinking something like the following would be quite helpful. 1. `known_size(::Type{AbstractArray}) = nothing` to indicate that that an `AbstractArray` should have a size, but its undefined because the...

Currently, there is still some unexpected behavior still happening for concrete `StaticArray` types. ``` import ArrayInterface as Arr A = SMatrix{3,3}(1:9) T = typeof(A) Arr.known_size(A) # OK --> (3, 3)...

Do you think this might solve [issue #1010](https://github.com/JuliaArrays/StaticArrays.jl/issues/1010)?

I started getting this warning when I followed the advice given in [Known issues and workarounds](https://github.com/julia-vscode/julia-vscode/wiki/Known-issues-and-workarounds#revisejl) on loading Revise at startup. Is this workaround no longer needed? I haven't noticed...