Invalid tuple for second-level TLD as input

[elceef]

>>> tld.__version__
'0.12.3'
>>> parse_tld('co.uk', fix_protocol=True)
('co.uk', 'co.uk', '')
# desired: ('uk', 'co', '')
>>> parse_tld('gov.pl', fix_protocol=True)
('gov.pl', 'gov.pl', '')
# desired: ('pl', 'gov', '')

[barseghyanartur]

That behaviour is correct.

• Private domains start at line 10646.
• gov.pl starts BEFORE that at line 5626
• co.uk starts BEFORE that at line 6421

[elceef]

Please note that:

• pl starts BEFORE gov.pl at line 5590
• uk starts BEFORE co.uk at line 6419

[barseghyanartur]

@elceef:

I think you don't understand the concept behind the TLD list. Since co.uk is in the list, it is considered a TLD. The only thing we separate here is public and private TLDs.

from tld import parse_tld                                                                                                                                   

parse_tld('co.uk', fix_protocol=True)                                                                                                                       
# ('co.uk', 'co.uk', '')

parse_tld('hey.uk', fix_protocol=True)                                                                                                                      
# ('uk', 'hey', '')

[elceef]

Respectfully, I think you miss the point being that both uk and co.uk are TLD, both are present in the list and uk precedes co.uk.

[barseghyanartur]

@elceef:

Your views slightly clash with an issue reported (and fixed) earlier #51

tld version 0.9.6 did behave as you now wish it would.

Let's discuss this further.

[elceef]

Input is inconsistent with the output:

>>> '.'.join(parse_tld('co.uk', fix_protocol=True))
'co.uk.co.uk.'

In this case and similar uk should have higher priority over co.uk and other second-level domains.