Path to this page:
Subject: CVS commit: pkgsrc/net/py-tldextract
From: Adam Ciarcinski
Date: 2023-11-03 09:17:33
Message id: 20231103081733.171AAFA2B@cvs.NetBSD.org
Log Message:
py-tldextract: updated to 5.0.1
5.0.1 (2023-10-17)
* Bugfixes
* Indicate MD5 not used in a security context (FIPS compliance)
* Misc.
* Increase typecheck aggression
5.0.0 (2023-10-11)
* Breaking Changes
* Migrate `ExtractResult` from `namedtuple` to `dataclass`
* This means no more iterating/indexing/slicing/unpacking the result
object returned by this library. It is no longer a tuple. You must
directly reference the fields you're interested in.
For example, the
following will no longer work.
```python
tldextract.extract("example.com")[1:3]
# TypeError: 'ExtractResult' object is not subscriptable
```
Instead, use the following.
```python
ext = tldextract.extract("example.com")
(ext.domain, ext.suffix)
```
* Bugfixes
* Drop support for EOL Python 3.7
* Misc.
* Switch from pycodestyle and Pylint to Ruff
* Consolidate config files
* Type tests
* Require docstrings in tests
* Remove obsolete tests
4.0.0 (2023-10-11)
* **Breaking** bugfixes
* Always include suffix if private suffix enabled and private suffix exists
* Add a 4th field `is_private: bool`, to the `ExtractResult`
`namedtuple`, indicating whether the extraction came from the PSL's
private domains or not.
* **This could cause issues when iterating over the tuple and assuming
only 3 fields.**
* Previously, the docs promoted iteration to rejoin parts of the tuple.
This is better achieved by individual access of fields of interest
(e.g. `ExtractResult.subdomain`) or convenience properties (e.g.
`ExtractResult.{fqdn,registered_domain}`).
This is the same content as version 3.6.0, originally released 2023-09-19,
which was yanked.
Files: