Installing the python bindings
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 160
- Forks
- 113
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
Currently the python bindings are "installed" by copying them to a pre-designated path. In python, the general pattern is to use setuptools, distutils or something similar to let python do this automatically.
In my forked library i made a commit https://github.com/odlgroup/STIR/commit/a9a6388865f0c532211c25abfe407ba8c1a265c3 that does exactly this. You can use it if you want.
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 reviewing the current Python binding installation entry point and the referenced STIR fork commit a9a6388865f0c532211c25abfe407ba8c1a265c3. Compare the existing copy-based process with the setuptools or distutils approach shown there. Done means the bindings install through Python's standard packaging workflow rather than requiring manual copying.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100