Skip to content

Implement equivalent of --readonly option for testing with new infrastructure #9852

Closed as not planned

Description

@astrofrog

In #9726 I refactored the infrastructure of the core package, but one option I was not immediately able to translate to the new infrastructure was the --readonly option to test. See #9726 (comment) for more details. This issue is a reminder that we should find a way to ensure that no files are written outside of temporary directories during tests. I'm assigning myself, but if anyone wants to tackle this please let me know as any help would be appreciated!

Activity

  1. added this to the v4.1 milestone on Jan 9, 2020
  2. self-assigned this
    on Jan 9, 2020
  3. modified the milestones: v4.1, v4.1.1 on Apr 30, 2020
  4. modified the milestones: v4.1.1, v4.2.1 on Nov 25, 2020
  5. modified the milestones: v4.2.1, v4.2.2 on Apr 8, 2021
  6. pllim commented on Apr 28, 2021

    @pllim
    Member

    It's been over a year. Can I just remove the milestone?

  7. modified the milestones: v4.2.2, v4.3.2 on Jul 27, 2021
  8. removed this from the v4.3.2 milestone on Mar 10, 2023
  9. astrofrog commented on Jun 26, 2025

    @astrofrog
    MemberAuthor

    I'm not sure that this can be done with the current infrastructure, nor has there been a strong desire for this, so I am going to just close this.

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions