An error occurred fetching the project authors.
- 14 Aug, 2017 1 commit
-
-
Iliya Manolov authored
@Tyagov @luke /reviewed-on nexedi/slapos!212
-
- 25 Jul, 2017 1 commit
-
-
Łukasz Nowak authored
-
- 21 Jun, 2017 1 commit
-
-
Iliya Manolov authored
@luke @Tyagov In Jupyter notebooks users could enter the url of their `Base_executeJupyter` function, but [it now gets filled in automatically](https://lab.nexedi.com/nexedi/slapos/blob/2f2a5ad0/software/ipython_notebook/template/ERP5kernel.py.jinja#L10). This makes the `%erp5_url` magic redundant which is why we can remove it. This commit also removes all mentions of `%erp5_url` in the kernel output and `custom.js`. /reviewed-on nexedi/slapos!185
-
- 12 Jun, 2017 1 commit
-
-
Iliya Manolov authored
@Tyagov @luke This MR adds the following to all Jupyter notebooks: - A warning when a user inputs a reference that has already been used in one of his old Jupyter notebooks. - Some extra information when entering magics such as the remaining required magics. - Entering the reference MUST now be the last magic entered(otherwise the reference check doesn't work). - A small addition to the message at the top of the notebook for the command ```%notebook_set_title``` Also, do note that the edited kernel uses files from [this commit](nexedi/erp5@4a3e5173) from my erp5 repo, so the changes there must be available for the kernel to work. [This merge request](nexedi/erp5!283) addresses those changes. Sample screenshot: ![Screenshot](/uploads/a34e0b70b991302539c572ad4344ba56/Screenshot.png) /reviewed-on nexedi/slapos!177
-
- 11 Jul, 2016 1 commit
-
-
Douglas authored
@Tyagov this is the slapos part of nexedi/erp5!131. It includes: - Documentation on top on each Jupyter notebook about why and how we use the environment object. - astor egg, used to convert abstract syntax tree objects back to source code. /reviewed-on nexedi/slapos!76
-
- 18 Dec, 2015 1 commit
-
-
Ayush Tiwari authored
ERP5 kernel basic info/workflow: 1. User enters code on notebook cell and executes 2. Code is sent to kernel via websockets 3. Kernel sends request to ERP5 4. Code is executed by ERP5 and the result is returned back via request. 5. Result is received and rendered on the notebook frontend. 6. Other message formats such as error and status are also conveyed by the Kernel. [ kirr: in IPython notebook speak kernel is something that allows IPython notebook server side to talk to execution backend. ERP5 kernel is a thing that allows ipython notbook to talk to ERP5 (with help on-ERP5-server special bt5 installed which accepts and executes commands). The bt5 to handle notebook calls on ERP5 side - erp5-data-notebook - is proposed to be merged into erp5.git on nexedi/erp5!29 ] /initially-reviewed-by @kirr, @Tyagov (in a lot of places, last time on nexedi/slapos!33)
-