Releases: john-kurkowski/tldextract
Releases · john-kurkowski/tldextract
5.1.3
What's Changed
- Bugfixes
- Documentation
- Clarify how to use your own definitions
- Clarify first-successful definitions vs. merged definitions
- Misc.
Contributors
Full Changelog: 5.1.2...5.1.3
5.1.2
5.1.1
What's Changed
- Bugfixes
- Fix path join on Windows (#314)
- Support Python 3.12
Contributors
Full Changelog: 5.1.0...5.1.1
5.1.0
What's Changed
- Features
- Docs
- Improve clarity of absolute path (#312)
- Misc.
- Extract all testing deps from tox.ini to pyproject.toml extras (#310)
- Work around responses type union error, in tests
New Contributors
- @chhao-hao made their first contribution in #311
- @vimagick made their first contribution in #313
Contributors
Full Changelog: 5.0.1...5.1.0
5.0.1
What's Changed
- Bugfixes
- Indicate MD5 not used in a security context (FIPS compliance) (#309)
- Misc.
- Increase typecheck aggression
New Contributors
- @CharlesB2 made their first contribution in #309
Full Changelog: 5.0.0...5.0.1
5.0.0
What's Changed
- Breaking Changes
- Migrate
ExtractResult
fromnamedtuple
todataclass
(#306)-
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.tldextract.extract("example.com")[1:3] # TypeError: 'ExtractResult' object is not subscriptable
Instead, use the following.
ext = tldextract.extract("example.com") (ext.domain, ext.suffix)
-
- Migrate
- Bugfixes
- Drop support for EOL Python 3.7
- Misc.
- Switch from pycodestyle and Pylint to Ruff (#304)
- Consolidate config files
- Type tests
- Require docstrings in tests
- Remove obsolete tests
Contributors
Full Changelog: 4.0.0...5.0.0
4.0.0
What's Changed
- Breaking bugfixes
- Always include suffix if private suffix enabled and private suffix exists (#300)
- Add a 4th field
is_private: bool
, to theExtractResult
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}
).
- Add a 4th field
- Always include suffix if private suffix enabled and private suffix exists (#300)
Contributors
Full Changelog: 3.5.0...4.0.0
This is the same content as version 3.6.0, originally released 2023-09-19,
which was yanked.
3.5.0
What's Changed
New Contributors
Contributors
Full Changelog: 3.4.4...3.5.0