Proposal to remove env from call to Popen#62
Closed
anthonyjclark wants to merge 1 commit intogoogle:mainfrom
Closed
Proposal to remove env from call to Popen#62anthonyjclark wants to merge 1 commit intogoogle:mainfrom
env from call to Popen#62anthonyjclark wants to merge 1 commit intogoogle:mainfrom
Conversation
Contributor
|
The |
Member
This file contains hidden or 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
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.
The current version of
_run_ffmpegcallsPopenwith an empty environment:This causes a difficult-to-understand error on my machine:
I tracked down the error, and it happens because I used pixi to install
ffmpeg. This will install astubat~/.pixi/bin/ffmpeg. The_get_ffmpeg_pathfunction will find the stub just fine, but the stub cannot find the actual exectuable when the environment is clobbered.This is easiest to replicate in bash:
I had a few options:
media.set_ffmpeg("/home/ajc/.pixi/envs/ffmpeg/bin/ffmpeg")env={}from the call toPopenI think the second choice is better. The first requires a full, hard-coded path (or resolving from the home directory, which I suppose it OK, but hard to remember after a few months).
I searched through the history of the
_run_ffmpegfunction and I did not find a reason for clobbering the environment. Please let me know if I am mistaken!