Skip to content

Expose custom safe_repr config #3427

Closed
#3438
Closed
Expose custom safe_repr config#3427
#3438
Assignees
sl0thentr0py

Description

@sl0thentr0py
sl0thentr0py
opened on Aug 9, 2024

@sl0thentr0py Thanks, yes, I think we prefer option 2 - the option for a custom repr function to be tried in safe_repr (my current understanding of how everything works is that this will both solve our needs and reduce the likelihood of this bug to creeping back in).

Thanks for giving us the choice 🙂

Originally posted by @philipstarkey in #3409 (comment)

Activity

  1. sl0thentr0py
    self-assigned this
    on Aug 12, 2024
  2. sl0thentr0py
    closed this as completedin #3438on Aug 12, 2024
  3. sl0thentr0py
    closed this as completedin 4858996on Aug 12, 2024

  4. sl0thentr0py commented on Aug 12, 2024

    @sl0thentr0py
    sl0thentr0py
    on Aug 12, 2024
    MemberAuthor

    @philipstarkey merged, will be in next release

  5. sthagen
    added a commit that references this issue on Aug 13, 2024

    Expose custom_repr function that precedes safe_repr invocation in ser…

    4858996
  6. arjennienhuis
    added a commit that references this issue on Sep 30, 2024

    Expose custom_repr function that precedes safe_repr invocation in ser…

    cb28ad2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions