You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However currently the UTF-8 and BOM check is done in the SecurityTXT class, not the Parser class, could the following code mode to the Parser class? This would of course change the Parser from accepting utf-8 to bytes.
With the new version we changed the parser to accept bytes instead of the string and the get_str function has been moved to the parser as was requested in your comment. Now if you use the parser directly you will still see the BOM error.
This is added in version 0.9.3
Thanks for fixing:
However currently the UTF-8 and BOM check is done in the
SecurityTXT
class, not theParser
class, could the following code mode to theParser
class? This would of course change the Parser from accepting utf-8 to bytes.sectxt/sectxt/__init__.py
Lines 422 to 435 in ad85c74
Since Internet.nl uses the Parser class this would remove the need to duplicate these UTF-8 and BOM checks in Internet.nl.
The text was updated successfully, but these errors were encountered: