fix: handle non-string input in Replace validator gracefully

[binggao1230]

The Replace validator calls re.Pattern.sub() directly on the input value. When passed a non-string type (int, None, list, etc.), this raises an unhandled TypeError instead of the expected Invalid exception.

This matches the behavior of the Match validator, which already catches TypeError and raises a proper Invalid error with a descriptive message.

Before (crashes):

>>> from voluptuous.validators import Replace
>>> Replace('hello', 'goodbye')(42)
TypeError: expected string or bytes-like object, got 'int'

After:

>>> from voluptuous.validators import Replace
>>> Replace('hello', 'goodbye')(42)
voluptuous.error.MatchInvalid: expected string or buffer

Changes:

• Replace._call_ now catches TypeError and raises MatchInvalid
• Added test_replace_non_string_input covering int, None, list, and custom message cases

[binggao1230]

Rebased onto master and dropped the unrelated quote-style churn from the diff — it's now just the Replace fix and its test.

[alecthomas]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4c75e63f90

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid swallowing TypeError from replacement callbacks

When substitution is a callable accepted by re.Pattern.sub, any TypeError raised inside that callback is now misreported as invalid input. In combinators such as Any, the resulting MatchInvalid is caught and another branch may silently accept the value, hiding a real callback defect; limit the conversion to TypeErrors caused by an incompatible input value.

Useful? React with 👍 / 👎.

[binggao1230]

Addressed in 80d3204: Replace now validates regex input compatibility before running sub(), so TypeError from a callable replacement propagates unchanged. Added coverage for callback failures and valid bytes-like inputs.