30 KiB

Raw Blame History

(type-translations)=

Type translations

In order to communicate between Python and JavaScript, we "translate" objects between the two languages. Depending on the type of the object we either translate the object by implicitly converting it or by proxying it. By "converting" an object we mean producing a new object in the target language which is the equivalent of the object from the source language, for example converting a Python string to the equivalent a JavaScript string. By "proxying" an object we mean producing a special object in the target language that forwards requests to the source language. When we proxy a JavaScript object into Python, the result is a {py:class}~pyodide.ffi.JsProxy object. When we proxy a Python object into JavaScript, the result is a {js:class}~pyodide.ffi.PyProxy object. A proxied object can be explicitly converted using the explicit conversion methods {py:meth}JsProxy.to_py() <pyodide.ffi.JsProxy.to_py> and {js:func}PyProxy.toJs() <pyodide.ffi.PyProxy.toJs>.

Python to JavaScript translations occur:

when returning the final expression from a {js:func}pyodide.runPython call,
when importing Python objects into JavaScript
when passing arguments to a JavaScript function called from Python,
when returning the results of a Python function called from JavaScript,
when accessing an attribute of a {js:class}~pyodide.ffi.PyProxy

JavaScript to Python translations occur:

when importing from the js module
when passing arguments to a Python function called from JavaScript
when returning the result of a JavaScript function called from Python
when accessing an attribute of a {py:class}~pyodide.ffi.JsProxy

:class: warning

Any time a Python to JavaScript translation occurs, it may create a
{js:class}`~pyodide.ffi.PyProxy`. To avoid memory leaks, you must store the {js:class}`~pyodide.ffi.PyProxy` and
{js:func}`~pyodide.ffi.PyProxy.destroy` it when you are done with it. See
{ref}`call-py-from-js` for more info.

Round trip conversions

Translating an object from Python to JavaScript and then back to Python is guaranteed to give an object that is equal to the original object. Furthermore, if the object is proxied into JavaScript, then translation back unwraps the proxy, and the result of the round trip conversion is the original object (in the sense that they live at the same memory address).

Translating an object from JavaScript to Python and then back to JavaScript gives an object that is === to the original object. Furthermore, if the object is proxied into Python, then translation back unwraps the proxy, and the result of the round trip conversion is the original object (in the sense that they live at the same memory address). There are a few exceptions:

NaN is converted to NaN after a round trip but NaN !== NaN,
{js:data}null is converted to {js:data}undefined after a round trip, and
a {js:data}BigInt will be converted to a {js:data}Number after a round trip unless its absolute value is greater than {js:data}Number.MAX_SAFE_INTEGER (i.e., 2^53).

Implicit conversions

We implicitly convert immutable types but not mutable types. This ensures that mutable Python objects can be modified from JavaScript and vice-versa. Python has immutable types such as {py:class}tuple and {py:class}bytes that have no equivalent in JavaScript. In order to ensure that round trip translations yield an object of the same type as the original object, we proxy {py:class}tuple and {py:class}bytes objects.

(type-translations_py2js-table)=

Python to JavaScript

The following immutable types are implicitly converted from Python to JavaScript:

Python	JavaScript
{py:class}`int`	{js:data}`Number` or {js:data}`BigInt`*
{py:class}`float`	{js:data}`Number`
{py:class}`str`	{js:data}`String`
{py:class}`bool`	{js:data}`Boolean`
{py:data}`None`	{js:data}`undefined`

* An {py:class}int is converted to a {js:data}Number if the absolute value is less than or equal to {js:data}Number.MAX_SAFE_INTEGER otherwise it is converted to a {js:data}BigInt. (If the browser does not support {js:data}BigInt then a {js:data}Number will be used instead. In this case, conversion of large integers from Python to JavaScript is lossy.)

(type-translations_js2py-table)=

JavaScript to Python

The following immutable types are implicitly converted from JavaScript to Python:

JavaScript	Python
{js:data}`Number`	{py:class}`int` or {py:class}`float` as appropriate*
{js:data}`BigInt`	{py:class}`int`
{js:data}`String`	{py:class}`str`
{js:data}`Boolean`	{py:class}`bool`
{js:data}`undefined`	{py:data}`None`
{js:data}`null`	{py:data}`None`

* A {js:data}Number is converted to an {py:class}int if the absolute value is less than or equal to {js:data}Number.MAX_SAFE_INTEGER and its fractional part is zero. Otherwise, it is converted to a {py:class}float.

Proxying

Any of the types not listed above are shared between languages using proxies that allow methods and some operations to be called on the object from the other language.

(type-translations-jsproxy)=

Proxying from JavaScript into Python

When most JavaScript objects are translated into Python a {py:class}~pyodide.ffi.JsProxy is returned. The following operations are currently supported on a {py:class}~pyodide.ffi.JsProxy:

Python	JavaScript
`str(proxy)`	`x.toString()`
`proxy.foo`	`x.foo`
`proxy.foo = bar`	`x.foo = bar`
`del proxy.foo`	`delete x.foo`
`hasattr(proxy, "foo")`	`"foo" in x`
`proxy(...)`	`x(...)`
`proxy.foo(...)`	`x.foo(...)`
{any}`proxy.new(...)<JsProxy.new>`	`new X(...)`
`len(proxy)`	`x.length` or `x.size`
`foo in proxy`	`x.has(foo)` or `x.includes(foo)`
`proxy[foo]`	`x.get(foo)`
`proxy[foo] = bar`	`x.set(foo, bar)`
`del proxy[foo]`	`x.delete(foo)`
`proxy1 == proxy2`	`x === y`
`proxy.typeof`	`typeof x`
`iter(proxy)`	`x[Symbol.iterator]()`
`next(proxy)`	`x.next()`
`await proxy`	`await x`

Note that each of these operations is only supported if the proxied JavaScript object supports the corresponding operation. See {py:class}the JsProxy API docs <pyodide.ffi.JsProxy> for the rest of the methods supported on {py:class}~pyodide.ffi.JsProxy. Some other code snippets:

for v in proxy:
    # do something

is equivalent to:

for (let v of x) {
  // do something
}

The {py:func}dir method has been overloaded to return all keys on the prototype chain of x, so dir(x) roughly translates to:

function dir(x) {
  let result = [];
  do {
    result.push(...Object.getOwnPropertyNames(x));
  } while ((x = Object.getPrototypeOf(x)));
  return result;
}

As a special case, JavaScript {js:class}Array, {js:class}HTMLCollection, and {js:class}NodeList are container types, but instead of using array.get(7) to get the 7th element, JavaScript uses array[7]. For these cases, we translate:

Python	JavaScript
`proxy[idx]`	`array[idx]`
`proxy[idx] = val`	`array[idx] = val`
`idx in proxy`	`idx in array`
`del proxy[idx]`	`array.splice(idx)`

If you need to access the fields in a JavaScript object, you must use obj.field_name or if the name of the field is not a valid Python identifier, getattr(obj, "field name"). If you want to access the fields of the object like obj["field name"] you can use {py:meth}~pyodide.ffi.JsProxy.as_object_map:

from pyodide.code import run_js

obj = run_js(
    """
    ({
      a: 7,
      b: 9,
      $c: 11
    })
    """
)
obj_map = obj.as_object_map()
assert obj_map["$c"] == 11

Another special case comes from the fact that Python reserved words cannot be used as attributes. For instance, {js:func}Array.from and {js:meth}Promise.finally cannot be directly accessed because they are Python SyntaxErrors. Instead we access these attributes with Array.from_ and Promise.finally_. Similarly, to access from Python, o.from_ you have to use o.from__ with two underscores (since a single underscore is used for o.from). This is reflected in the dir of a JsProxy:

from pyodide.code import run_js
o = run_js("({finally: 1, return: 2, from: 3, from_: 4})")
assert set(dir(o)) == {"finally_", "return_", "from_", "from__"}

(type-translations-pyproxy)=

Proxying from Python into JavaScript

When most Python objects are translated to JavaScript a {js:class}~pyodide.ffi.PyProxy is produced.

Fewer operations can be overloaded in JavaScript than in Python, so some operations are more cumbersome on a {js:class}~pyodide.ffi.PyProxy than on a {py:class}~pyodide.ffi.JsProxy. The following operations are supported:

JavaScript	Python
`foo in proxy`	`hasattr(x, 'foo')`
`proxy.foo`	`x.foo`
`proxy.foo = bar`	`x.foo = bar`
`delete proxy.foo`	`del x.foo`
`Object.getOwnPropertyNames(proxy)`	`dir(x)`
`proxy(...)`	`x(...)`
`proxy.foo(...)`	`x.foo(...)`
`proxy.length`	`len(x)`
`proxy.has(foo)`	`foo in x`
`proxy.get(foo)`	`x[foo]`
`proxy.set(foo, bar)`	`x[foo] = bar`
`proxy.delete(foo)`	`del x[foo]`
`proxy.type`	`type(x)`
`proxy[Symbol.iterator]()`	`iter(x)`
`proxy.next()`	`next(x)`
`await proxy`	`await x`

:class: warning

Make sure to destroy PyProxies when you are done with them to avoid memory leaks.

```javascript
let foo = pyodide.globals.get('foo');
foo();
foo.destroy();
foo(); // throws Error: Object has already been destroyed
```

Explicit Conversion of Proxies

(type-translations-pyproxy-to-js)=

Python to JavaScript

Explicit conversion of a {js:class}~pyodide.ffi.PyProxy into a native JavaScript object is done with the {js:func}~pyodide.ffi.PyProxy.toJs method. You can also perform such a conversion in Python using {py:func}~pyodide.ffi.to_js which behaves in much the same way. By default, the {js:func}~pyodide.ffi.PyProxy.toJs method does a recursive "deep" conversion, to do a shallow conversion use proxy.toJs({depth : 1}). In addition to the normal type conversion, the {js:func}~pyodide.ffi.PyProxy.toJs method performs the following explicit conversions:

Python	JavaScript
{py:class}`list`, {py:class}`tuple`	{js:class}`Array`
{py:class}`dict`	{js:class}`Map`
{py:class}`set`	{js:class}`Set`
{external:doc}`a buffer <c-api/buffer>`*	{js:class}`TypedArray`

* Examples of buffers include {py:class}bytes objects and numpy {external+numpy:ref}arrays.

If you need to convert {py:class}dict instead to {js:data}Object, you can pass {js:func}Object.fromEntries as the dict_converter argument: proxy.toJs({dict_converter : Object.fromEntries}).

See {ref}buffer_tojs for the behavior of {js:func}~pyodide.ffi.PyProxy.toJs on buffers.

:class: warning

The {js:func}`~pyodide.ffi.PyProxy.toJs` method can create many proxies at arbitrary
depth. It is your responsibility to manually {js:meth}`~pyodide.ffi.PyProxy.destroy`
these proxies if you wish to avoid memory leaks. The `pyproxies` argument to
{js:meth}`~pyodide.ffi.PyProxy.toJs` is designed to help with this:
```js
let pyproxies = [];
proxy.toJs({pyproxies});
// Do stuff
// pyproxies contains the list of proxies created by `toJs`. We can destroy them
// when we are done with them
for(let px of pyproxies){
    px.destroy();
}
proxy.destroy();
```
As an alternative, if you wish to assert that the object should be fully
converted and no proxies should be created, you can use
`proxy.toJs({create_proxies : false})`. If a proxy would be created, a
{py:exc}`~pyodide.ffi.ConversionError` is raised instead.

(type-translations-jsproxy-to-py)=

JavaScript to Python

Explicit conversion of a {py:class}~pyodide.ffi.JsProxy into a native Python object is done with the {py:meth}JsProxy.to_py() <pyodide.ffi.JsProxy.to_py> method. By default, the {py:meth}~pyodide.ffi.JsProxy.to_py method does a recursive "deep" conversion, to do a shallow conversion use proxy.to_py(depth=1). The {py:meth}~pyodide.ffi.JsProxy.to_py method performs the following explicit conversions:

JavaScript	Python
{js:class}`Array`	{py:class}`list`
{js:data}`Object`*	{py:class}`dict`
{js:class}`Map`	{py:class}`dict`
{js:class}`Set`	{py:class}`set`

* {py:meth}~pyodide.ffi.JsProxy.to_py will only convert an {js:data}Object into a dictionary if its constructor is {js:data}Object, otherwise the object will be left alone. Example:

class Test {};
window.x = { "a" : 7, "b" : 2};
window.y = { "a" : 7, "b" : 2};
Object.setPrototypeOf(y, Test.prototype);
pyodide.runPython(`
    from js import x, y
    # x is converted to a dictionary
    assert x.to_py() == { "a" : 7, "b" : 2}
    # y is not a "Plain Old JavaScript Object", it's an instance of type Test so it's not converted
    assert y.to_py() == y
`);

In JavaScript, {js:class}Map and {js:class}Set keys are compared using object identity unless the key is an immutable type (meaning a {js:data}String, a {js:data}Number, a {js:data}BigInt, a {js:data}Boolean, {js:data}undefined, or {js:data}null). On the other hand, in Python, {py:class}dict and {py:class}set keys are compared using deep equality. If a key is encountered in a {js:class}Map or {js:class}Set that would have different semantics in Python than in JavaScript, then a {py:exc}~pyodide.ffi.ConversionError will be thrown. Also, in JavaScript, true !== 1 and false !== 0, but in Python, True == 1 and False == 0. This has the result that a JavaScript map can use true and 1 as distinct keys but a Python {py:class}dict cannot. If the JavaScript map contains both true and 1 a {py:exc}~pyodide.ffi.ConversionError will be thrown.

Functions

(call-py-from-js)=

Calling Python objects from JavaScript

If a Python object is callable, the proxy will be callable too. The arguments will be translated from JavaScript to Python as appropriate, and the return value will be translated from JavaScript back to Python. If the return value is a {js:class}~pyodide.ffi.PyProxy, you must explicitly destroy it or else it will be leaked.

An example:

let test = pyodide.runPython(`
    def test(x):
        return [n*n for n in x]
    test
`);
let result_py = test([1,2,3,4]);
// result_py is a PyProxy of a list.
let result_js = result_py.toJs();
// result_js is the array [1, 4, 9, 16]
result_py.destroy();

If a function is intended to be used from JavaScript, you can use {py:func}~pyodide.ffi.to_js on the return value. This prevents the return value from leaking without requiring the JavaScript code to explicitly destroy it. This is particularly important for callbacks.

let test = pyodide.runPython(`
    from pyodide.ffi import to_js
    def test(x):
        return to_js([n*n for n in x])
    test
`);
let result = test([1,2,3,4]);
// result is the array [1, 4, 9, 16], nothing needs to be destroyed.

If you need to use a key word argument, use {js:func}~pyodide.ffi.PyCallable.callKwargs. The last argument should be a JavaScript object with the key value arguments.

let test = pyodide.runPython(`
    from pyodide.ffi import to_js
    def test(x, *, offset):
        return to_js([n*n + offset for n in x])
    to_js(test)
`);
let result = test.callKwargs([1,2,3,4], { offset : 7});
// result is the array [8, 12, 16, 23]

(call-js-from-py)=

Calling JavaScript functions from Python

What happens when calling a JavaScript function from Python is a bit more complicated than calling a Python function from JavaScript. If there are any keyword arguments, they are combined into a JavaScript object and used as the final argument. Thus, if you call:

f(a=2, b=3)

then the JavaScript function receives one argument which is a JavaScript object {a : 2, b : 3}.

When a JavaScript function is called, if the return value not a {js:class}Promise, a {js:class}Generator, or an {js:class}AsyncGenerator, any arguments that are PyProxies that were created in the process of argument conversion are also destroyed. If the result is a {js:class}~pyodide.ffi.PyProxy it is also destroyed.

As a result of this, if a {js:class}~pyodide.ffi.PyProxy is persisted to be used later, then it must either be copied using {js:meth}~pyodide.ffi.PyProxy.copy in JavaScript, or it must be created with {py:func}~pyodide.ffi.create_proxy or {py:func}~pyodide.ffi.create_once_callable. If it's only going to be called once use {py:func}~pyodide.ffi.create_once_callable:

from pyodide import create_once_callable
from js import setTimeout
def my_callback():
    print("hi")
setTimeout(create_once_callable(my_callback), 1000)

If it's going to be called many times use {py:func}~pyodide.ffi.create_proxy:

from pyodide import create_proxy
from js import document
def my_callback():
    print("hi")
proxy = pyodide.create_proxy(my_callback)
document.body.addEventListener("click", proxy)
# ...
# make sure to hold on to proxy
document.body.removeEventListener("click", proxy)
proxy.destroy()

When a JavaScript function returns a {js:class}Promise (for example, if the function is an {ref}async function), it is assumed that the {js:class}Promise is going to do some work that uses the arguments of the function, so it is not safe to destroy them until the {js:class}Promise resolves. In this case, the proxied function returns a Python {py:class}~asyncio.Future instead of the original {js:class}Promise. When the {js:class}Promise resolves, the result is converted to Python and the converted value is used to resolve the {py:class}~asyncio.Future. Then if the result is a {js:class}~pyodide.ffi.PyProxy it is destroyed. Any PyProxies created in converting the arguments are also destroyed at this point.

Similarly, if the return value is a {js:class}Generator or {js:class}AsyncGenerator, then the arguments (and all values sent to the generator) are kept alive until it is exhausted, or until {py:meth}~pyodide.ffi.JsGenerator.close is called.

Buffers

Using JavaScript Typed Arrays from Python

JavaScript {js:class}ArrayBuffer and {js:class}TypedArray objects are proxied into Python. Python can't directly access arrays if they are outside the WASM heap, so it's impossible to directly use these proxied buffers as Python buffers. You can convert such a proxy to a Python {py:class}memoryview using the {py:meth}~pyodide.ffi.JsProxy.to_py api. This makes it easy to correctly convert the array to a Numpy array using {py:func}numpy.asarray:

self.jsarray = new Float32Array([1,2,3, 4, 5, 6]);
pyodide.runPython(`
    from js import jsarray
    array = jsarray.to_py()
    import numpy as np
    numpy_array = np.asarray(array).reshape((2,3))
    print(numpy_array)
`);

After manipulating numpy_array you can assign the value back to jsarray using {py:meth}~pyodide.ffi.JsBuffer.assign:

pyodide.runPython(`
    numpy_array[1,1] = 77
    jsarray.assign(a)
`);
console.log(jsarray); // [1, 2, 3, 4, 77, 6]

The {py:meth}~pyodide.ffi.JsBuffer.assign and {py:meth}~pyodide.ffi.JsBuffer.assign_to methods can be used to assign a JavaScript buffer from / to a Python buffer which is appropriately sized and contiguous. The assignment methods will only work if the data types match, the total length of the buffers match, and the Python buffer is contiguous.

(buffer_tojs)=

Using Python Buffer objects from JavaScript

Python objects supporting the Python Buffer protocol are proxied into JavaScript. The data inside the buffer can be accessed via the {js:func}~pyodide.ffi.PyProxy.toJs method or the {js:func}~pyodide.ffi.PyBuffer.getBuffer method. The {js:func}~pyodide.ffi.PyProxy.toJs API copies the buffer into JavaScript, whereas the {js:func}~pyodide.ffi.PyBuffer.getBuffer method allows low level access to the WASM memory backing the buffer. The {js:func}~pyodide.ffi.PyBuffer.getBuffer API is more powerful but requires care to use correctly. For simple use cases the {js:func}~pyodide.ffi.PyProxy.toJs API should be preferred.

If the buffer is zero or one-dimensional, then {js:func}~pyodide.ffi.PyProxy.toJs will in most cases convert it to a single {js:class}TypedArray. However, in the case that the format of the buffer is 's', we will convert the buffer to a string and if the format is '?' we will convert it to an {js:class}Array of booleans.

If the dimension is greater than one, we will convert it to a nested JavaScript array, with the innermost dimension handled in the same way we would handle a 1d array.

An example of a case where you would not want to use the {js:func}~pyodide.ffi.PyProxy.toJs method is when the buffer is bitmapped image data. If for instance you have a 3d buffer shaped 1920 x 1080 x 4, then {js:func}~pyodide.ffi.PyProxy.toJs will be extremely slow. In this case you could use {js:func}~pyodide.ffi.PyProxy.getBuffer. On the other hand, if you have a 3d buffer shaped 1920 x 4 x 1080, the performance of {js:func}~pyodide.ffi.PyProxy.toJs will most likely be satisfactory. Typically, the innermost dimension won't matter for performance.

The {js:func}~pyodide.ffi.PyProxy.getBuffer method can be used to retrieve a reference to a JavaScript typed array that points to the data backing the Python object, combined with other metadata about the buffer format. The metadata is suitable for use with a JavaScript ndarray library if one is present. For instance, if you load the JavaScript ndarray package, you can do:

let proxy = pyodide.globals.get("some_numpy_ndarray");
let buffer = proxy.getBuffer();
proxy.destroy();
try {
  if (buffer.readonly) {
    // We can't stop you from changing a readonly buffer, but it can cause undefined behavior.
    throw new Error("Uh-oh, we were planning to change the buffer");
  }
  let array = new ndarray(
    buffer.data,
    buffer.shape,
    buffer.strides,
    buffer.offset,
  );
  // manipulate array here
  // changes will be reflected in the Python ndarray!
} finally {
  buffer.release(); // Release the memory when we're done
}

(type-translations-errors)=

Errors

All entrypoints and exit points from Python code are wrapped in JavaScript try blocks. At the boundary between Python and JavaScript, errors are caught, converted between languages, and rethrown.

JavaScript errors are wrapped in a {py:class}~pyodide.ffi.JsException. Python exceptions are converted to a {js:class}~pyodide.PythonError. At present if an exception crosses between Python and JavaScript several times, the resulting error message won't be as useful as one might hope.

In order to reduce memory leaks, the {js:class}~pyodide.PythonError has a formatted traceback, but no reference to the original Python exception. The original exception has references to the stack frame and leaking it will leak all the local variables from that stack frame. The actual Python exception will be stored in {py:data}sys.last_value so if you need access to it (for instance to produce a traceback with certain functions filtered out), use that.

:class: warning
If you make a {js:class}`~pyodide.ffi.PyProxy` of {py:data}`sys.last_value`, you should be especially
careful to {js:meth}`~pyodide.ffi.PyProxy.destroy` it when you are done with it, or
you may leak a large amount of memory if you don't.

The easiest way is to only handle the exception in Python:

pyodide.runPython(`
def reformat_exception():
    from traceback import format_exception
    # Format a modified exception here
    # this just prints it normally but you could for instance filter some frames
    return "".join(
        format_exception(sys.last_type, sys.last_value, sys.last_traceback)
    )
`);
let reformat_exception = pyodide.globals.get("reformat_exception");
try {
    pyodide.runPython(some_code);
} catch(e){
    // replace error message
    e.message = reformat_exception();
    throw e;
}

Importing Objects

It is possible to access objects in one language from the global scope in the other language. It is also possible to create custom namespaces and access objects on the custom namespaces.

(type-translations_using-py-obj-from-js)=

Importing Python objects into JavaScript

A Python global variable in the __main__ global scope can be imported into JavaScript using the {js:meth}pyodide.globals.get() <pyodide.ffi.PyProxyWithGet.get> method. Given the name of the Python global variable, it returns the value of the variable translated to JavaScript.

let x = pyodide.globals.get("x");

As always, if the result is a {js:class}~pyodide.ffi.PyProxy and you care about not leaking the Python object, you must destroy it when you are done. It's also possible to set values in the Python global scope with {js:meth}pyodide.globals.set() <pyodide.ffi.PyProxyWithSet.set> or remove them with {js:meth}pyodide.globals.delete() <pyodide.ffi.PyProxyWithSet.delete>:

pyodide.globals.set("x", 2);
pyodide.runPython("print(x)"); // Prints 2

If you execute code with a custom globals dictionary, you can use a similar approach:

let my_py_namespace = pyodide.globals.get("dict")();
pyodide.runPython("x=2", my_py_namespace);
let x = my_py_namespace.get("x");

To access a Python module from JavaScript, use {js:func}~pyodide.pyimport:

let sys = pyodide.pyimport("sys");

(type-translations_using-js-obj-from-py)=

Importing JavaScript objects into Python

JavaScript objects in the {js:data}globalThis global scope can be imported into Python using the js module.

When importing a name from the js module, the js module looks up JavaScript attributes of the {js:data}globalThis scope and translates the JavaScript objects into Python.

import js
js.document.title = 'New window title'
from js.document.location import reload as reload_page
reload_page()

You can also assign to JavaScript global variables in this way:

pyodide.runPython("js.x = 2");
console.log(window.x); // 2

You can create your own custom JavaScript modules using {js:func}pyodide.registerJsModule and they will behave like the js module except with a custom scope:

let my_js_namespace = { x : 3 };
pyodide.registerJsModule("my_js_namespace", my_js_namespace);
pyodide.runPython(`
    from my_js_namespace import x
    print(x) # 3
    my_js_namespace.y = 7
`);
console.log(my_js_namespace.y); // 7

If the JavaScript object's name is a reserved Python keyword, the {py:func}setattr function can be used to access the object by name within the js module::

lambda = (x) => {return x + 1};
//'from js import lambda' will cause a Syntax Error, since 'lambda' is a Python reserved keyword. Instead:
pyodide.runPython(`
    import js
    js_lambda = getattr(js, 'lambda')
    print(js_lambda(1))
    `);

If a JavaScript object has a property that is a reserved Python keyword, the {py:func}setattr and {py:func}getattr function can be used to access that property by name:

people = {global: "lots and lots"};
//Trying to access 'people.global' will raise a Syntax Error, since 'global' is a Python reserved keyword. Instead:
pyodide.runPython(`
    from js import people
    setattr(people, 'global', 'even more')
    print(getattr(people, 'global'))
    `);

30 KiB Raw Blame History

Type translations

Round trip conversions

Implicit conversions

Python to JavaScript

JavaScript to Python

Proxying

Proxying from JavaScript into Python

Proxying from Python into JavaScript

Explicit Conversion of Proxies

Python to JavaScript

JavaScript to Python

Functions

Calling Python objects from JavaScript

Calling JavaScript functions from Python

Buffers

Using JavaScript Typed Arrays from Python

Using Python Buffer objects from JavaScript

Errors

Importing Objects

Importing Python objects into JavaScript

Importing JavaScript objects into Python

30 KiB

Raw Blame History