Finishing python module support
Nobody has claimed this yet.
- #482 by @KipHamiltons — closed without merging
- Dominant language
- C++
- Stars
- 41
- Forks
- 22
- Avg merge
- 1h 48m
- Merged PRs (30d)
- 1
Description
Currently there exists an abandoned, ancient PR (#146) which works towards adding python modules (and nice stuff for opencl, "which is only useful if we think we will be implementing more OpenCL-based modules"). Writing modules is harder than it could be, in large part because C++ is much more time consuming that python.
Python wouldn't be a long term solution for any given module (because it's python, and that's not in the same performance tier as C++), but it would really help faster iteration of modules and module concepts, which is especially important come robocup crunchtimes.
This is a really cool project, and I don't think we should forget about it. Having the ability to write modules in python would be huge.
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.
Research direction
Start by reviewing the abandoned PR #146 and the closed PR #482 to understand the previous approaches to Python module support. Then establish the current module entry points and define how Python modules should be written and validated; done means modules can be implemented in Python for faster iteration without losing the existing C++ path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100