)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":935,"name":"James Page","email":"ringo.page@gmail.com","username":"james-page"},"change_message_id":"b96131a026326cf582c29dcca12f7c07fe7913d8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9a95bc51_0070bb15","updated":"2025-01-22 10:18:12.000000000","message":"Removal - https://review.opendev.org/c/openstack/keystone/+/939778","commit_id":"3c0b6b372d82396bbf6c9331b63286fad0fb2830"},{"author":{"_account_id":27900,"name":"Artem Goncharov","email":"artem.goncharov@gmail.com","username":"gtema"},"change_message_id":"18827764b22589fb3cc10f64b363e875f48b8125","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"668ff78e_4cf98662","updated":"2025-01-22 08:13:46.000000000","message":"support for crypt was deprecated in Keystone multiple years ago and is just there for \"upgrade\" reasons. When I was replacing the passlib we discussed already upcoming deprecation of crypt and agreed to still port it but drop it from the code once we need to start supporting py313. The change is fine but since we are not allowing new deployments to use crypt it makes no sense to pull new dependency and we can now simply drop the sha512_crypt method completely.","commit_id":"3c0b6b372d82396bbf6c9331b63286fad0fb2830"},{"author":{"_account_id":935,"name":"James Page","email":"ringo.page@gmail.com","username":"james-page"},"change_message_id":"8553a41a8661b555228989fa9a972b5464d693d3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"1a39cb43_a7e029cf","in_reply_to":"668ff78e_4cf98662","updated":"2025-01-22 10:01:51.000000000","message":"Thanks for the additional context - I\u0027ll abandon this change and raise a new one to remove the module completely.","commit_id":"3c0b6b372d82396bbf6c9331b63286fad0fb2830"}]}