René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Docs: reframe shared CONSTANTS as an application-startup contract","articleBody":"The shared module-level `CONSTANTS` is sound — it's the only channel that reaches parses happening inside code you don't own (helpers, pipelines, third-party libraries using nameparser internally), the same justification `logging` and `locale` have. The gotchas all come from mutating it casually. The docs should state that as a contract instead of warning about it:\n\n\u003e `CONSTANTS` is for application-level configuration, set once at startup. For anything scoped — one dataset, one library, one test — pass your own `Constants` instance.\n\nChanges:\n- customize.rst: lead the customization docs with the contract; demote the \"Potential Gotcha\" section to a consequence of violating it rather than a surprise property of the API\n- `nameparser/config/__init__.py` module docstring: same reframe (it currently teaches the `None` sentinel first)\n- Fold in the three-spelling vocabulary from #260 once `Constants.copy()` exists\n\nNo code changes. Depends on #260 only for the vocabulary mention; the reframe itself is true today.\n","author":{"url":"https://github.com/derek73","@type":"Person","name":"derek73"},"datePublished":"2026-07-06T08:14:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/262/python-nameparser/issues/262"}