py5coding on Nostr: While testing what would have been today's #py5 release I discovered a critical bug ...
While testing what would have been today's #py5 release I discovered a critical bug on macOS computers with Intel CPUs. The bug is kind of obscure, only affecting users of those machines and Jupyter who first run a Sketch using the default renderer and later run a Sketch with an OpenGL renderer.
I can certainly fix this, but not tonight.
I did want to do a release but it is more important to get this right. Let me re-address the code and I'll do a release when everything checks out.
Published at
2024-12-12 23:07:55Event JSON
{
"id": "1994e14d33c8318c5f2271ad88dd696210c1cf4930a8784751c214cd4b61cb88",
"pubkey": "84ee38e8a3fd005f79ad54ce399885a0a0493f3345fcfcdd92353994b25bc89b",
"created_at": 1734044875,
"kind": 1,
"tags": [
[
"t",
"py5"
],
[
"proxy",
"https://fosstodon.org/users/py5coding/statuses/113642364974635481",
"activitypub"
]
],
"content": "While testing what would have been today's #py5 release I discovered a critical bug on macOS computers with Intel CPUs. The bug is kind of obscure, only affecting users of those machines and Jupyter who first run a Sketch using the default renderer and later run a Sketch with an OpenGL renderer.\n\nI can certainly fix this, but not tonight.\n\nI did want to do a release but it is more important to get this right. Let me re-address the code and I'll do a release when everything checks out.",
"sig": "0793f2addedfbd6c16f325f8bdd0dc3c496c0cb526f3e6837a70a8f28c2a1733ac910d61d5ea47333f38ff2508e32f960517c683d5ab3b4fa2d1ae20cccfc3a6"
}