Metadata-parser

Latest version: v0.12.1

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 14

0.8.0

this bump introduces 2 new arguments and some changed behavior:

- `search_head_only=None`. previously the meta/og/etc data was only searched in the document head (where expected as per HTML specs).
after indexing millions of pages, many appeared to implement this incorrectly of have html that is so off specification that
parsing libraries can't correctly read it (for example, Twitter.com).
This is currently implemented to default from None to True, but future versions will default to `False`.
This is marked for a future default of `search_head_only=False`

- `raise_on_invalid`. default False. If True, this will raise a new exception: InvalidDocument if the response
does not look like a proper html document

0.7.4

- more aggressive attempts to get the peername.

0.7.3

- this will now try to cache the `peername` of the request (ie, the remote server) onto the peername attribute

0.7.2

- applying a `strip()` to the "title". bad authors/cms often have whitespace.

0.7.1

- added kwargs to docstrings
- `get_metadata_link` behavior has been changed as follows:
* if an encoded uri is present (starts with `data:image/`)
** this will return None by default
** if a kwarg of `allow_encoded_uri=True` is submitted, will return the encoded url (without a url prefix)

0.7.0

- merged https://github.com/jvanasco/metadata_parser/pull/9 from xethorn
- nested all commands to `log` under `__debug__` to avoid calls on production when PYTHONOPTIMIZE is set

Page 7 of 14

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.