This file is indexed.

/usr/share/doc/python-zc.customdoctests/spidermonkey.txt is in python-zc.customdoctests 1.0.1-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
Javascript and Python-Spidermonkey support
------------------------------------------

.. This file shows some examples of using spidermonkey APIs in doctests.

To wire this up, you'd use something like::

   import doctest, zc.customdoctests.js

   test_suite = doctest.DocTestSuite(
       parser=zc.customdoctests.js.parser,
       setUp=zc.customdoctests.js.spidermonkeySetUp)

Or, with manuel::

    test_suite = manuel.testing.TestSuite(
        manuel.doctest.Manuel(parser=zc.customdoctests.js.parser) +
        manuel.doctest.Manuel(parser=zc.customdoctests.js.eq_parser) +
        manuel.doctest.Manuel() +
        manuel.capture.Manuel(),
        'spidermonkey.txt',
        setUp=zc.customdoctests.js.spidermonkeySetUp)

Note that zc.customdoctests doesn't require spidermonkey, so you need
to install spidermonkey seperately if you want to use it.

An advantage of using manuel is that you can use multiple parsers in
the same document.  In the example, above, 2 javascript example
syntaxes (described below) as well as the standard doctest syntax are
supported.  This document is run with manuel to allow all 3 syntaxes.

For the rest of this document, we'll show examples of JavaScript
doctests as well as helper APIs used to support JavaScript and to
integrate JavaScript and Python.

Javascript doctests use a "js>" prompt (as used in rhino and the
spidermonkey interpreter)::

    js> 2 +
    ... 'Hi world' // doctest: +ELLIPSIS
    u'2Hi...

Assignments return values.  This can generate annoying output
in doctests::

    js> ob = {a: 1, b: 2}
    [object Object]

If you're using manuel, you can avoid this by using js!::

    js! x = 3

which suppresses expression values.

load and print functions (similar to those found in rhino) are
provided.  For example, given a javascript file, double.js::

   function double (x) {
       return x*2;
   }

.. -> src

   >>> with open('double.js', 'w') as f:
   ...     f.write(src)

We can load the file::

    js> load('double.js')
    js> double(10)
    20

We can print values::

    js> print('Hi')
    Hi

A python object provides access to the open function and the os
module::

    js> python.os.path.exists('double.js')
    True

    js! f = python.open('double.js')
    js> print(f.read())
    function double (x) {
        return x*2;
    }
    <BLANKLINE>

    js> f.close()


If you're using manuel, you can intermix Python and and JavaScript
examples and there are a number of APIs to facilitate using Python and
JavaScript together.

There's an add_js_global function to copy data from Python::

    >>> add_js_global('y', 1)

    js> y
    1

There's also a js object that provides attribute access to js globals::

    >>> js.x
    3

    >>> js.z = 4

    js> z
    4

You can also call this to run JS code without returning the resulting value::

    >>> js('a = x + y')

    js> a
    4