TL;DR Iâve been working on a WebGPU optimized inference and autograd library called webgpu-torch with an API that matches PyTorch. The goal is to run neural networks in the browser at speeds comparable to a Linux workstation. Many kernels have been implemented and its design is easily extensible. Itâs available on NPM now and works in both the browser and Node.js!
Iâve been working on pygfx, a Python graphics library based on wgpu (the successor to OpenGL). I wrote a post on it's background https://almarklein.org/wgpu.html
This project is close to my heart, visualisation is what got me into Python. For scientific Pythonistaâs pygfx might still a bit low-level - the idea is that others can build high-level libraries on top.
pip install python Back in 2018 when Kushal first proposed PEP 582, several of us at the core devs sprint sat down and tried to brainstorm requirements for python workflow tooling that âgrows withâ users from novice to expert, and how well PEP 582 could meet them. (I posted notes.) One of Kushalâs main requirements, based on his experience teaching beginners, is that you should only have to install one thing to get started. So, that leaves two possibilities: either installing Python had to give ...
⨠If you are interested in Python and WebAssembly, @brettcannon wrote up a great article on getting started. There are even some new Trove classifiers for PyPI to mark packages as WebAssembly-friendly.
Testing a Python project using the WASI build of CPython with pytest - https://fosstodon.org/@brettcannon/109723994706754087
Wrote a blog post about what it took to run the test suite for `packaging` using #Python #WASI : https://snarky.ca/testing-a-project-using-the-wasi-build-of-cpython-with-pytest/ As part of this work, PyPI got some new classifiers for WebAssembly: Environment :: WebAssembly Environment :: WebAssembly :: Emscripten Environment :: WebAssembly :: WASI They're a bit empty since they are literally 2 hours old. đ
@anildash I don't think enough people have realized how incredibly valuable the robust universal sandboxing provided by WASM is going to be
I genuinely don't want to run code written by other people that's NOT in a sandbox at this point: even if I trust them, do I also trust them not to have written any bugs?
WASM to me represents the freedom to run code on my machines again!
PEP 703 by Sam Gross and sponsored by @ambv on Making the Global Interpreter Lock Optional in CPython is now a public draft:
https://peps.python.org/pep-0703/
Others and I contributed some context on why this would help improve the efficiency and maintainability of #Python code in the context of #DataScience, #MachineLearning #DeepLearning and more generally in scientific programming / #scipy contexts.
Feel free to discuss this draft here: https://discuss.python.org/t/pep-703-making-the-global-interpreter-lock-optional/22606
CPythonâs global interpreter lock (âGILâ) prevents multiple threads from executing Python code at the same time. The GIL is an obstacle to using multi-core CPUs from Python efficiently. This PEP proposes adding a build configuration (--disable-gil) to...
PEP703: making the global interpreter lock (GIL) optional in CPython. Draft. This is big news. Many more hurdles ahead #python
Sponsor: Ĺukasz Langa Note that the "Discussions-To" field is a placeholder. I'll update the field once the PEP is an official draft and the corresponding thread is created on http://discuss.pytho...
Seth Larson
Simon Willison
Almar
Nathaniel J. Smith
Jeff Triplett
Olivier Grisel
Anthony Shaw 
The Oatmeal
