QuantConnect / QuantConnect/Lean
Improve python debugger exposed data
Open
Nobody has claimed this yet.
depth
feature
- Dominant language
- C#
- Stars
- 21.7k
- Forks
- 5.3k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 34
Description
Expected Behavior
- When debugging only relevant and accurate data is presented to the user
Actual Behavior
- There are multiple non relevant sources presented and we should be showing snake_case
Potential Solution
- Would require researching/reviewing the source of this information. Ideally we can solve this generically. Believe an attribute can be used to hide for the debugger, not sure how to adjust the name to pep 8 though,
Reproducing the Problem
Debug python algorithm
System Information
N/A
Checklist
- I have completely filled out this template
- I have confirmed that this issue exists on the current
masterbranch - I have confirmed that this is not a duplicate issue by searching issues
- I have provided detailed steps to reproduce the issue
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
Start by reproducing the issue while debugging a Python algorithm and identify where the debugger's exposed data is assembled. Review the source of the displayed values and determine how irrelevant sources and naming are selected; done means only relevant, accurate data is shown using snake_case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100