Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: drop response.charset because charset deprecated (#206)
I took a quick peek at upstream to see if this has any backwards-breaking issues whereby we'd need to check the `werkzeug` version, but from my reading it looks it should be fine most of the time. Also, this was deprecated back in April's `2.3.0` release and then removed in the recent `3.0.0` release, so I suspect most of our userbase will have already migrated to those versions. Given this lib is a dev-tooling library not typically used in production, I'm not too worried about ensuring we support the 0.01% case where someone is using an old version of `werkzeug` + a custom charset. More context: * pallets/werkzeug#2602 * pallets/werkzeug#2641 * pallets/werkzeug#2768
- Loading branch information
9571d06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, but I keep with the problem at the line 260 [content = content.encode(response.charset)]