#markupsafe — Public Fediverse posts

slsa-github-generator v2 now uses upload/download-artifact v4, so I can update those in all the Pallets projects. Turns out the publish workflow for most projects didn't need any changes at all. Only MarkupSafe, with multiple build jobs, needed a little change to use different upload names and combine their downloads. https://github.com/pallets/markupsafe/commit/f4905079ef7573d5c1e8fe1f291f1e353050bc87 #Python #Flask #MarkupSafe #GitHub #SLSA

MarkupSafe speedup saga continues: my coworker contributed a PR to implement them in Rust now. It uses some pretty clever speedups based on other serialization libraries they surveyed. If anyone is comfortable with Rust, we would appreciate reviews and feedback: https://github.com/pallets/markupsafe/pull/438 #Python #RustLang #PyO3 #Flask #MarkupSafe

Update on my "remove MarkupSafe's C speedups" post: @tonybaloney swooped in and found a simple change that make the speedups ~40% faster in the cases where they had become slower. Turns out, if plain strings are the most probable thing you'll be escaping, you should check for that first, not last. So the speedups remain in place. https://github.com/pallets/markupsafe/pull/434 #Python #MarkupSafe #Flask

Python has seen significant performance improvements in the last few releases. MarkupSafe has a C extension to speed up operations, but it's now *slower* in many cases than the plain Python implementation. Having a C extension increases the difficulty of maintenance, builds, releases, and installs. I'm wondering if it's time to drop the speedups. https://github.com/pallets/markupsafe/issues/433 #Python #MarkupSafe #Flask

Got this error with Ansible on my Mac:
ERROR: No module named 'markupsafe'

Found this: https://ansiblepilot.medium.com/ansible-troubleshooting-error-no-module-named-markupsafe-8c9f45dae5b5

Solved it by (re)installing python-markupsafe: ansible; brew uninstall ansible python-markupsafe; brew install ansible python-markupsafe; ansible

#ansible #homebrew #markupsafe