ofek / ofek/pyapp

Load modules from memory instead of extracting to disk?

Open
#219 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
2k
Forks
65
PR merge metrics
No merged PRs in 30d

Description

Hello, I'm new to PyApp, but recently got it working. I have previously mostly used Pyinstaller. Though I also tried PyOxidizer, until it was deprecated. One of the things I was amazed by PyOxidizer was just how blazing fast the built binaries were. My understanding is that speed came from it's ability to load modules from memory, rather than extracting them to disk.

I was hoping PyApp was doing something similar, considering it is also using Rust to compile the binary, but it seems not. Have you used PyOxidizer yourself? Is loading modules from memory something that PyApp might consider as an option?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by reading the linked PyOxidizer FAQ and tracing PyApp’s current extraction-to-disk path; done would be a maintainer-approved, scoped decision on whether in-memory module loading should be supported and what implementation work it entails.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
build-system, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.