-
-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
packaging issues with pipx, usage of sys.executable -m #218
Comments
I think I should just broaden the question to, is it possible to create usable virtual environments using a PyOxidizer binary? Using the following configuration, I got pretty close: [[embedded_python_config]]
raw_allocator = "jemalloc"
[[embedded_python_config]]
sys_paths = ["$ORIGIN/lib"]
ignore_environment = false
filesystem_importer = true
[[packaging_rule]]
type = "stdlib-extensions-policy"
policy = "all"
[[packaging_rule]]
type = "stdlib"
include_source = true
exclude_test_modules = true
install_location = "app-relative:lib"
include_resources = true
[[embedded_python_run]]
mode = "repl" I can run
However, the resulting symlinked virtual environment cannot be used.
Even with trying to provide the environment variables for the python path, it still can't be used:
|
Linking this issue (#141) which talks about creating a mode to allow for a |
Also linking this issue which more explicitly talks about building a |
pipx
creates virtualenvs by calling out to the terminal using:run([DEFAULT_PYTHON, "-m", "venv", "--clear", self.root])
. whereDEFAULT_PYTHON
issys.executable
.Is it possible to call out to or expose the embedded python within
PyOxidizer
?My top level CLI is
pipx
but I imagine maybe I can expose the underlying python aspipx python
? In which case I can just change myDEFAULT_PYTHON
and things can work as is?I know that it's also possible to create virtualenvs with
import venv; venv.create('.venv')
but that would be a lot of code to rewrite.The text was updated successfully, but these errors were encountered: