REPL Done Right

REPL Done Right

Abc432bb0450574a25b15ff23d399d5a?s=128

Vladimir Pouzanov

October 20, 2012
Tweet

Transcript

  1. None
  2. REPL Vladimir Pouzanov @farcaller

  3. why do we need a REPL?

  4. calculator

  5. Quick hacks on the code

  6. Solving a problem

  7. Python vs. bash anyone?

  8. Math™ stuff

  9. read-eval-print?

  10. read

  11. parse the code

  12. write code

  13. read

  14. docs

  15. eval

  16. bullet-proof

  17. print

  18. informative

  19. color coding

  20. color coding

  21. details on demand

  22. IPython

  23. awesome

  24. simple to start

  25. None
  26. learn on the go

  27. None
  28. docs!

  29. None
  30. source

  31. None
  32. None
  33. None
  34. None
  35. 20% cooler

  36. %edit

  37. None
  38. None
  39. None
  40. None
  41. None
  42. None
  43. None
  44. None
  45. None
  46. %edit is much more powerful!

  47. %paste / %cpaste

  48. None
  49. %pastebin

  50. None
  51. None
  52. None
  53. None
  54. %magic

  55. %%ruby

  56. %%perl too!

  57. terminal REPL

  58. GUI

  59. event loop integration

  60. Qt GUI

  61. None
  62. None
  63. rich formatting

  64. None
  65. kernels

  66. [IPKernelApp]  To  connect  another   client  to  this  kernel,  use:

    [IPKernelApp]  -­‐-­‐existing   kernel-­‐73976.json
  67. None
  68. None
  69. None
  70. None
  71. None
  72. notebook

  73. all the features

  74. advanced markup

  75. persistence

  76. None
  77. GUI too!

  78. None
  79. We all have possibilities we don't know about. We can

    do things we don't even dream we can do. Dale Carnegie
  80. Thanks! mail@farcaller.net @farcaller