Skip to content

Document caveats of zipfile.Path around name sanitization #123726

Closed

Description

@jaraco

Advertise that zipfile.Path does not do any name sanitization and it's the responsibility of the caller to check the inputs, etc.

I think documenting the caveats would be good.

Originally posted by @obfusk in #123270 (comment)

Linked PRs

Activity

  1. jaraco commented on Sep 9, 2024

    @jaraco
    MemberAuthor

    @abj101 expressed interest in working on a documentation issue relating to #123270. Please take some time to understand the concern and consider how you might want to approach communicating the concern to the reader. Feel free to ask questions or describe a draft change in this issue, or create a PR. See the documentation section of the devguide for advice on how to contribute documentation changes. Thanks for offering to help.

  2. AffanShaikhsurab commented on Jan 13, 2025

    @AffanShaikhsurab
    Contributor

    Hi, I would love to contribute and be a part of this! Could someone please assign this to me?

  3. swastim01 commented on Feb 9, 2025

    @swastim01

    Hi if this issue is unassigned, I'd like to take it up.

  4. jaraco commented on Feb 17, 2025

    @jaraco
    MemberAuthor

    Since Affan offered first, let's let them take the first stab at it. Swasti - perhaps you could review the proposal. If there's no proposal by March 15, feel free to take it on. Affan, please keep us apprised and let us know if you've stopped working on it or have questions.

  5. added a commit that references this issue on Feb 25, 2025
  6. AffanShaikhsurab commented on Feb 25, 2025

    @AffanShaikhsurab
    Contributor

    Hi @jaraco ,

    I’ve created a pull request to address this issue by adding a note to the zipfile.Path documentation clarifying that it doesn’t sanitize filenames. This is my first contribution to CPython, so I’d really appreciate it if you could review the PR and let me know if I’ve missed anything or if there’s anything I need to improve.

    Thank you for your guidance!

  7. added a commit that references this issue on Mar 8, 2025
  8. added 2 commits that reference this issue on Mar 8, 2025
  9. added 2 commits that reference this issue on Mar 8, 2025
  10. added a commit that references this issue on Mar 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

docsDocumentation in the Doc direasy

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions