Closed malev closed 8 years ago
Just reproduced the build locally.
There is something I was doing wrong when calling the new install scripts on nbpresent that came over here. I'm looking into it...
Oof... it seems like nb_anacondacloud might be publishing private by default now? Is this a thing I might have set?
Ah, indeed: i had manually made my "untitled" package private, which ended being the same name (based on the notebook name).
@bollwyvl if you already have a package in AS it will not change the permissions already setup. If you are creating a new package (notebook) it will be public by default
Quick overview looks good, but I will review in depth tomorrow (still I have to finish reviewing the latest changes upstream)... btw, nice work guys!
Went with #21 instead.
Do not merge till
jupyter 4.2
is out.@bollwyvl