Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is the "in-place" update of Context a bad idea? #112

Open
benoit74 opened this issue Dec 6, 2024 · 2 comments
Open

Is the "in-place" update of Context a bad idea? #112

benoit74 opened this issue Dec 6, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request question Further information is requested
Milestone

Comments

@benoit74
Copy link
Contributor

benoit74 commented Dec 6, 2024

See #92 (comment)

@benoit74 benoit74 added enhancement New feature or request question Further information is requested labels Dec 6, 2024
@benoit74 benoit74 added this to the 0.1 milestone Dec 6, 2024
@benoit74 benoit74 self-assigned this Dec 6, 2024
@benoit74
Copy link
Contributor Author

benoit74 commented Dec 6, 2024

The (only) use-case so far is for tests, where I need to have a default context initialized in init so that I avoid to have to create a context in every test (even with a fixture, it would be pain) but I can still setup it again for tests needing to test this Context behavior.

Suggestions of enhancements welcomed of course, I just didn't found a way to do it differently and do not see how calling it could be done by accident and/or lead to a significant problem

@benoit74
Copy link
Contributor Author

Moving to "later", does not seem important to fix now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant