#2006 Overwriting sys.argv[0] leaves no remaining methods to identify the actual sys.argv[0] Issue created by jamesmeador As of the 2.1.91 release, sys.argv[0] is no longer a reliable option for identifying the executed script as called. For example, creating a symlink to a pex, then calling that symlink yields a sys.argv[0] that does not point to the symlink. The PEX environment variable also does not point to the symlink. Are there any known remaining ways to obtain argv[0] as provided by the calling binary? pantsbuild/pex

#2006 Overwriting sys.argv[0] leaves no remaining methods to identify the actual sys.argv[0] Issue closed as completed by jsirois pantsbuild/pex

#2006 Overwriting sys.argv[0] leaves no remaining methods to identify the actual sys.argv[0] Issue closed as completed by jsirois pantsbuild/pex