nprofile1q…hqepl nprofile1q…z7wec i think that is just wrong, i think the ...

2026-05-04 11:03:30 UTC

nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqfxems53wrpy52zewypx0rx4pt2g265zqtd3jaa9myh5zq7nscpfsqhqepl (nprofile…qepl) nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqgw6a7ynjevw7ljtn73tdm0xfwyzp56f7u43j38eyp9mj4tn7d4psyz7wec (nprofile…7wec) i think that is just wrong, i think the interpreter should be stable and not externalize these costs or technical debt on the users. distros are the right way to do it. can you explain me why the modules in `lib/python3.x` cannot be reused over versions? what would break between v3.12 and v3.13 for example? would py, pyc, or .so files break? did the python c api change in a breaking way? and if so why cannot this be done in a gracefully degrading way?

Author Public Key

npub1hzrmll8k8p3hv0r3yczfgjarfnmtge62h2we44vxlk3c805lqlyqe4fe37

Seen on

wss://relay.ditto.pub

Show more details

Published at

2026-05-04 11:03:30 UTC

Kind type

1 Short Text Note

Event JSON

{ "id": "a2ad7b2aaa56358ca4b098e9159b55f26d723c6c01bd50cd72140acc32df8f6c", "pubkey": "b887bffcf63863763c712604944ba34cf6b4674aba9d9ad586fda383be9f07c8", "created_at": 1777892610, "kind": 1, "tags": [ [ "p", "49b3b8522e1849450b2e204cf19aa15a90ad50405b632ef4bb25e8207a70c053", "wss://relay.ditto.pub" ], [ "p", "43b5df1272cb1defc973f456ddbcc971041a693ee563289f2409772aae7e6d43", "wss://relay.ditto.pub" ], [ "p", "6bccaf1a89e4c87fde8c0cb8bac9efb2aab0b1033dc90ba9678289192bea0642", "wss://relay.ditto.pub" ], [ "p", "cbcdffca8d6546b5343531d7bce5cded993a97bc1cd584011f8bdbb33e449467", "wss://relay.ditto.pub" ], [ "e", "049107e63a1fa6dae652bcb66fc5975c17b9a6bb7e157c6e803f0d15e32139bf", "wss://relay.ditto.pub", "reply" ], [ "proxy", "https://chaos.social/users/stf/statuses/116515970100160053", "activitypub" ], [ "client", "Mostr", "31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr", "wss://relay.ditto.pub" ] ], "content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqfxems53wrpy52zewypx0rx4pt2g265zqtd3jaa9myh5zq7nscpfsqhqepl nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqgw6a7ynjevw7ljtn73tdm0xfwyzp56f7u43j38eyp9mj4tn7d4psyz7wec i think that is just wrong, i think the interpreter should be stable and not externalize these costs or technical debt on the users. distros are the right way to do it. can you explain me why the modules in `lib/python3.x` cannot be reused over versions? what would break between v3.12 and v3.13 for example? would py, pyc, or .so files break? did the python c api change in a breaking way? and if so why cannot this be done in a gracefully degrading way?", "sig": "0dae7af623b48d4f307e0824f5aac6673d15a2e26181c929baa1590cd8b986c39543b957b688027f10998e7f228fde8be0cce2242805d487f5ba71b13b19849d" }

stf on Nostr: nprofile1q…hqepl nprofile1q…z7wec i think that is just wrong, i think the ...