Workflow for driver development
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 459
- Forks
- 359
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 73
Description
Relayed from @spauka :
When developing a driver, reloading a module doesn't update existing objects; this is standard Python behavior. This means that the old Instrument object stays around with the old definition, and the natural way to get to the new state is to stop and restart Python.
It would be nice if there were a way to easily find and delete the old Instrument object while reloading the module.
Contributor guide
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
The issue names no files, tests, or entry points. Start by tracing how Python module reloads affect existing Instrument objects and how drivers expose those objects. Done means providing a documented way to find and delete the old Instrument object so driver development can continue without restarting Python.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100