Allow persistent pyembed runtime projects #717
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pipes through to a (currently unused) runtime_path field on the StandalonePythonExecutableBuilder.
Skehmatics
changed the title
Skehmatics
changed the title
|
Very timely, thank you. I just started looking at PyOxidizer this week and thought I was going crazy when I couldn't get the persistent build to work. |
|
Commenting back to say that this patch worked fine for me. Thanks! @indygreg would love to see this get merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow the use of pyoxidizer's build system in a project created via
init-rust-project.This adds a
runtimeoption toPythonDistribution.to_python_executable()that specifies the path of the Rust project, and defines it duringinit-rust-projectWith this, applications that are happy to continue utilizing pyoxidizer's python resource discovery system can continue doing so while still allowing custom Rust code to be included in the final executable.
Closes #335