Skip to content

Commit 268b192

Browse files
derek73claude
andcommitted
Document that parsing never modifies the shared config
The shared-configuration warning in customize.rst now has a precise boundary worth stating: after the parse-time mutation fix, instances can only affect each other through explicit add/remove calls, so concurrent parsing against the shared CONSTANTS is safe. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 parent 46d4a8d commit 268b192

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

docs/customize.rst

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -429,6 +429,9 @@ When you modify the configuration, by default this will modify the behavior all
429429
HumanName instances. This could be a handy way to set it up for your entire
430430
project, but it could also lead to some unexpected behavior because changing
431431
the config on one instance could modify the behavior of another instance.
432+
Parsing itself never modifies the configuration — only your own ``add`` and
433+
``remove`` calls do — so the shared instance is safe to read concurrently,
434+
e.g. parsing names on multiple threads.
432435

433436
.. doctest:: module config
434437
:options: +ELLIPSIS, +NORMALIZE_WHITESPACE

0 commit comments

Comments
 (0)