pytest-dev / pytest-dev/pytest-forked

Useful against pollution of interpreter state

Open
#8 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
Python
Stars
83
Forks
29
PR merge metrics
No merged PRs in 30d

Description

Just wanted to point that this package can be a useful protection against "pollution" of the interpreter state.

For example when testing behaviour of custom imports, given the global state of sys, and the cache mechanisms, having boxed processes prevent unknowingly reusing a module imported from another test.
And there might be more cases like this one.

We should probably gather them in one place (README ?) as they might be a bit esoteric for the newcomer, and it would be useful to pin them down.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the README and review the issue's example about custom imports, global sys state, and module caches. Gather the documented use cases for boxed processes in one place, including this interpreter-state protection scenario. Done means the README explains these less-obvious use cases clearly for newcomers.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.