This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ablack
Recipients ablack, agnosticdev, joseph.hackman, r.david.murray, sdbowman
Date 2020-07-24.19:35:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1595619340.88.0.184611951144.issue32958@roundup.psfhosted.org>
In-reply-to
Content
joseph.hackman

I don't think that the 63 character limit on a label is the problem specifically, merely it's application. 

The crux of my issue was that credentials passed with the url in a basic-authy fashion (as some services require) count against the label length. For example, this would trigger the error:

h = "https://ablack:very_long_api_key_0123456789012345678901234567890123456789012345678901234567890123@www.example.com"

Since the first label would be treated as:
 "ablack:very_long_api_key_0123456789012345678901234567890123456789012345678901234567890123@www"

My specific issue goes away if any text up to / including an "@" in the first label section is not included in the label validation. I don't know off hand if that information is supposed to be included per the label in the DNS spec though.
History
Date User Action Args
2020-07-24 19:35:40ablacksetrecipients: + ablack, r.david.murray, joseph.hackman, agnosticdev, sdbowman
2020-07-24 19:35:40ablacksetmessageid: <1595619340.88.0.184611951144.issue32958@roundup.psfhosted.org>
2020-07-24 19:35:40ablacklinkissue32958 messages
2020-07-24 19:35:40ablackcreate