QMT_HTTP_API封装.py bug
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Open QMT_HTTP_API封装.py and inspect the safe_call usages around lines 128, 311, 404, and 412. Compare these calls with the issue’s requested context-bound methods, then verify that all listed cases use the intended context API without changing their surrounding behavior.
Written by the indexing model from the issue text.
Description
128行 :
ret = safe_call(get_open_date, stockcode)
应该改为
ret = safe_call(self.ctx().get_open_date, stockcode)
311:
ret = safe_call(timetag_to_datetime, timetag, fmt)
应该改为
ret = safe_call((self.ctx().timetag_to_datetime, timetag, fmt)
404:
ret = safe_call(get_etf_info, stockcode)
应该改为
ret = safe_call(self.ctx().get_etf_info, stockcode)
412:
ret = safe_call(get_etf_iopv, stockcode)
应该改为
ret = safe_call(self.ctx().get_etf_iopv, stockcode)
...
- Dominant language
- Python
- Stars
- 205
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
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.
More from Rockyzsu/QMT
-
买卖没有直接委托 Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
能不能搞个本地版本的？不用通过网络的 Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100