René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"TupleManager string inputs: cryptic ValueError for bare strings, silent key/value shredding for 2-char elements","articleBody":"`TupleManager` (and `RegexTupleManager`) inherit `dict.__init__` unchanged, so string inputs behave inconsistently with the guarded `SetManager` (#238):\n\n```python\nfrom nameparser.config import Constants, TupleManager\n\nConstants(capitalization_exceptions='ab')\n# ValueError: dictionary update sequence element #0 has length 1; 2 is required\n# loud, but names no argument and suggests no fix\n\nTupleManager(['ab', 'cd'])                   # {'a': 'b', 'c': 'd'} — silent\nConstants(capitalization_exceptions=['ii'])  # {'i': 'i'} — silent\n```\n\nThe bare-string case fails loudly but cryptically (dict internals, `ValueError` where the sibling set-backed args now raise a friendly `TypeError`). The worse case is the silent one: an iterable of 2-character strings is a valid dict-update sequence, so each string shreds into a key/value pair with no error — same family as #238 through the mapping constructor.\n\nFix: give `TupleManager` an `__init__` that rejects `str`/`bytes` outright (mirroring `SetManager._reject_bare_string`'s message style) and rejects non-tuple string *elements*, closing the 2-char variant.\n\nFound by review of PR #240 — pre-existing, unrelated to that change.","author":{"url":"https://github.com/derek73","@type":"Person","name":"derek73"},"datePublished":"2026-07-06T01:08:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/242/python-nameparser/issues/242"}