popsim-consortium / popsim-consortium/stdpopsim
transition liftOver maintanance code to use `concurrent.futures`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 144
- Forks
- 100
- Avg merge
- 2h 44m
- Merged PRs (30d)
- 2
Description
While reviewing #574, @jeromekelleher noted that using concurrent.futures for multiprocessing would make the code easier to understand and maintain.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the liftOver maintenance code and reviewing issue #574, including the rationale for using concurrent.futures. The work is done when the multiprocessing code has been transitioned without changing liftOver behavior, with the relevant tests still passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100