hard to attach processprotocol to an existing process
Open
Nobody has claimed this yet.
core
enhancement
new
priority-normal
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@mwhudson reported |
|---|---|
| Trac ID | trac#3856 |
| Type | enhancement |
| Created | 2009-05-26 12:35:56Z |
I have a desire to attach a process that already exists to a ProcessProtocol. This certainly doesn't seem to be easy.
Searchable metadata
trac-id__3856 3856
type__enhancement enhancement
reporter__mwh mwh
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__
time__1243341356000000 1243341356000000
changetime__1243629698000000 1243629698000000
version__None None
owner__
cc__exarkun
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 locating the ProcessProtocol and existing-process attachment APIs, then define the expected behavior and tests for attaching an already-running process; done should be a documented, tested way to perform that attachment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100