mathoudebine / mathoudebine/turing-smart-screen-python
seperate `lcd_comm` as library/driver (PIP package)
Nobody has claimed this yet.
- Dominant language
- Rich Text Format
- Stars
- 2.3k
- Forks
- 412
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? If so, please describe the problem.
One of my projects just wants the library/lcd/ files. I don't need any other files/folders like res, tools.. etc.
Those lcd_comm classes are used as drivers for this device.
Describe the feature/solution to your problem you'd like
I want to use those lcd_comm classes as pip packages
Describe alternatives you've considered / and or tested
Currently, I have to copy those files into my project. Which will be harder to maintain in the future.
Is there any better way to do it correctly?
If I want to do a pull request, how should I proceed?
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 with the files under library/lcd/ and the lcd_comm classes described in the issue. Review how the repository currently structures those files and what is needed to distribute them as a pip package. Done means the classes can be installed and imported without copying unrelated res or tools files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100