indygreg / indygreg/PyOxidizer
Building self-contained libraries?
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
I have quite a few Python web applications running on my server. Keeping these running over the years through Python upgrades and dependency churn is a pain in the ass, so it would be nice if I could do what I think amounts to "static linking" through PyOxidizer. Usually, my Python web applications are deployed with Apache + mod_wsgi: that is, they are modules that expose a well-known `application` callable.
Looking at the documentation, it appears to be very focused on creating executables. How feasible is it at this stage to create PyOxidizer-wrapped libraries?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the documentation for creating executables and the deployment model described with Apache and mod_wsgi. Determine what a PyOxidizer-wrapped library would need to expose for a well-known application callable, and define the feasibility boundaries before proposing implementation work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- backend, build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100