actions / actions/setup-python
provide python without RUNPATH for staticx-support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 739
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 1
Description
Description:
I want to use this project as GH action to generate a statically linked python binary using staticx.
While implementing the workflow I ran into https://github.com/JonathonReinhart/staticx/issues/188 due to the usage DT_RUNPATH.
It would be nice to have a setup-python version which does not use RUNPATH for use-cases like this.
Justification:
I understand that using RUNPATH simplifies the process of provinding a self-contained and reusable venv.
Unfortunately for running staticx that is bad because the generated binary will check the path defined by RUNPATH on the system running it and not be fully self-contained.
Are you willing to submit a PR?
Yes, but unfortunately I don't know TypeScript and cannot grasp the work required.
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
No files or tests are named. Start by tracing the TypeScript action entry point that installs or selects Python and identify where RUNPATH is introduced; done means a supported setup-python path can provide Python without RUNPATH and the behavior is validated for the staticx use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100