)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"eabe6402655391f1878c2e764d1a82528b3ccc7a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"63995625_94f28662","updated":"2025-10-20 06:37:25.000000000","message":"IIUC we switched to the new build since pypi.org started to refuse accepting uploads in the old format. so this would need testing somehow, maybe we need to create a release.test repo instead of release-test?","commit_id":"b56a3f0a671ed3bf89ca7acff810997fbb81f915"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"345883e9273906960dd2864636dd238fdacf5f38","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"03dfd14d_d7bcfa8d","updated":"2025-10-27 08:48:37.000000000","message":"thanks Tony! I haven\u0027t tested this, but looks fine, based on the commit message and the code. Maybe we can test this with some release and revert this patch if we see that what Jens wrote is true. (of course if someone has clear memory that pypi doesn\u0027t accept packages created with old setuptools, then we don\u0027t need to test this)","commit_id":"b56a3f0a671ed3bf89ca7acff810997fbb81f915"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"f4f6f8723e1f28bdf8d347a81c81fc32419b4247","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"bd27b01f_996acc58","updated":"2025-10-27 10:15:15.000000000","message":"thanks gents.   I\u0027ll check out the pypi aspect.   which is sad news to me.   in terms of testing do we have any way to check the full release process other than the release-test repo?","commit_id":"b56a3f0a671ed3bf89ca7acff810997fbb81f915"}]}