Due to the upgrade to charset-normalizer 2.0.4 guessing the encoding inside the tests did not work anymore and caused the umlaut tests to fail. Explicitly specifying the encoding on the requests' response object fixes this.fix-weird-encoding-problem-in-tests
부모
d87a42cf8e
커밋
41a0f64ff7
불러오는 중...
Reference in new issue