Skip to content
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

python: add __PYENV_LAUNCHER__ env var #525

Merged
merged 1 commit into from
Nov 9, 2014

Conversation

commodo
Copy link
Contributor

@commodo commodo commented Nov 9, 2014

Mostly useful for setuptools and pip during build.

Signed-off-by: Alexandru Ardelean ardeleanalex@gmail.com

Mostly useful for setuptools and pip during build.

Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
sbyx added a commit that referenced this pull request Nov 9, 2014
python: add __PYENV_LAUNCHER__ env var
@sbyx sbyx merged commit 52f72ea into openwrt:master Nov 9, 2014
@commodo commodo deleted the python-env-launcher branch November 11, 2014 19:31
jefferyto added a commit to jefferyto/openwrt-packages that referenced this pull request May 25, 2023
Setting __PYVENV_LAUNCHER__ for Python package builds was added in
a91a992, but neither the commit message
nor the pull request[1] explain its purpose in detail.

My guess is this was done to set the shebang for installed Python
scripts. We now have a Makefile recipe to set the shabang, so setting
this variable for this purpose is unnecessary.

It appears that Python 3.11 has changed the handling of this (internal)
environment variable, and setting it appears to be causing build errors
for all Python packages.

This removes setting __PYVENV_LAUNCHER__ for Python package builds.

[1]: openwrt#525

Fixes: openwrt#21162
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
jefferyto added a commit to jefferyto/openwrt-packages that referenced this pull request May 25, 2023
Setting __PYVENV_LAUNCHER__ for Python package builds was added in
a91a992, but neither the commit message
nor the pull request[1] explain its purpose in detail.

My guess is this was done to set the shebang for installed Python
scripts. We now have a Makefile recipe to set the shebang, so it would
be unnecessary to set this variable for this purpose.

It appears that Python 3.11 has changed the handling of this (internal)
environment variable, and setting it appears to be causing build errors
for all Python packages.

This removes setting __PYVENV_LAUNCHER__ for Python package builds.

[1]: openwrt#525

Fixes: openwrt#21162
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
jefferyto added a commit to jefferyto/openwrt-packages that referenced this pull request May 26, 2023
Setting __PYVENV_LAUNCHER__ for Python package builds was added in
a91a992, but neither the commit message
nor the pull request[1] explain its purpose in detail.

My guess is this was done to set the shebang for installed Python
scripts. We now have a Makefile recipe to set the shebang, so it would
be unnecessary to set this variable for this purpose.

It appears that Python 3.11 has changed the handling of this (internal)
environment variable, and setting it appears to be causing build errors
for all Python packages.

This removes setting __PYVENV_LAUNCHER__ for Python package builds.

[1]: openwrt#525

Fixes: openwrt#21162
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
(cherry picked from commit 9e95dff)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants