Anders Kaseorg

Yep, we’ve been following Tauri development with excitement for the last two years, and switching to it is [planned](https://zulip.readthedocs.io/en/latest/contributing/gsoc.html#electron-desktop-app).

I’m getting the same `Bad message (74)` error, and sysupgrade.openwrt.org seems to be responding to all requests with HTTP/2 502 (Bad Gateway). Edit: Seems to be working now.

This may want to wait until the future of `__future__.annotations` becomes less unclear (python/cpython#82786, python/cpython#93628, [PEP 649](https://peps.python.org/pep-0649/)).

It was fixed in Python 3.2: http://bugs.python.org/issue9003 http://docs.python.org/py3k/library/urllib.request.html#urllib.request.urlopen I recognize that it may be some time before mechanize gets ported to Python 3. But given that mechanize forks several other...

I’m not sure I understand. Like I said, there already is a patch against Python, which I linked to in my previous comment, and it was applied in Python 3.2....

> The problem with going that way in WASM is that making DOM API calls is more expensive than querying in-memory VDOM. The alternative to diffing with a virtual DOM...

SRI hashes were added in jazzband/webpack-bundle-tracker#59 with a different name (`assets.*.integrity` rather than `chunks.*.sriHash`).

Your output demonstrates that the problem persists with Rollup. (The warning from `rollup src.js` is about the exports *of `src.js`*, which don’t matter in this example. It can be appeased...

Still an issue.

@trumpet2012 That’s #532.