upstream/ipython Files · docs/attic/nbexample_output.py

Move crash handling to the application level and simplify class structure....

Move crash handling to the application level and simplify class structure. Starting to try to take real advantage of the refactoring, to have generic crash handling. This also lets us initialize the app without needing all the self.attempt() wrappers, since now there's a good system-wide crash handler at the app level (not inside the shell instance). I didn't yet remove the attempt() method because we may have occasional uses for it (we still do, but in one place only). I also removed some extra class layers that weren't quite needed. Creating classes solely for the purpose of passing parameters makes the code (IMO) harder to understand, I kept getting lost in parts of the class hierarchy. I think these changes provide the same flexibility but with easier to follow code (less things to remember, basically). What I tried to do was to use argument passing instead of inheritance for all cases I saw where the inheritance wasn't really adding new functionality. In some cases, this actually allowed me to remove methods that were effectively duplicated in the subclasses.

Brian E Granger - - Load All Authors

File last commit:

r1248:19e3b286


                r2403:08d6ac78

Download file

             nbexample_output.py
        
                    20 lines
            
             | 642 B
            
                | text/x-python
            
             |
                PythonLexer
            
             / docs / attic / nbexample_output.py
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      from notebook.markup import rest

      rest.title('This is a Python Notebook')

      rest.text("""\

      Some plain text, without any special formatting.

      Below, we define a simple function to add two numbers.""")

      def add(x,y):

          return x+y

      rest.text("Let's use it with x=2,y=3:")

      # This simply means that all code until the next markup call is to be executed

      # as a single call.  The editing screen should mark the whole group of lines

      # with a single In[NN] tag (like IPython does, but with multi-line capabilities)

      rest.input()

      add(2,3)

      # This output would appear on-screen (in the editing window) simply marked

      # with an Out[NN] tag

      rest.output("5")

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				from notebook.markup import rest

				rest.title('This is a Python Notebook')
				rest.text("""\
				Some plain text, without any special formatting.

				Below, we define a simple function to add two numbers.""")

				def add(x,y):
				return x+y

				rest.text("Let's use it with x=2,y=3:")
				# This simply means that all code until the next markup call is to be executed
				# as a single call. The editing screen should mark the whole group of lines
				# with a single In[NN] tag (like IPython does, but with multi-line capabilities)
				rest.input()
				add(2,3)
				# This output would appear on-screen (in the editing window) simply marked
				# with an Out[NN] tag
				rest.output("5")