Optimize wrappers
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- performance
Research direction
Start with the referenced python/lttoolbox.i lines 23-24 and inspect the wrapper entry points in this repository. Measure repeated dictionary loading for an Analyzer and the cost of reopening files; done should be demonstrated by performance evidence and tests covering the resulting wrapper behavior.
Written by the indexing model from the issue text.
Description
While our wrappers avoid the extra process overhead, I think they can still be improved.
e.g. we only need to run https://github.com/apertium/lttoolbox/blob/master/python/lttoolbox.i#L23-L24 one time for any given Analyzer object
On another note, we should also try to do something smarter instead of re-opening files everywhere (but this might be harder to get working).
@unhammer, is doing the first thing I mentioned (i.e. only loading the dictionary once) meaningful in terms of improving performance? Sounds to me like it would be.
- Dominant language
- Python
- Stars
- 35
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 apertium/apertium-python
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
apertium/apertium-python#109 · 2 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apertium/apertium-python#108 · 10 comments · 1 reaction ·
-
segfaultOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apertium/apertium-python#106 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apertium/apertium-python#105 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apertium/apertium-python#102 · 3 comments ·
All issues in apertium/apertium-python
Similar issues
-
adr
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kristofdegrave/homeassistant-smart-charging#1607 ·
Maintainers usually reply within 1 day
-
namespace operations
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
EclipseFdn/open-vsx.org#13665 ·
Maintainers usually reply within 1 day
-
doc good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
collective/icalendar#1865 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
canonical/opentelemetry-collector-operator#409 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
mozilla/addons-release-tests#1243 ·
Maintainers usually reply within 1 day