Oleg Broytman phd at phdru.name
Sat Mar 18 11:42:46 EDT 2017

• Previous message (by thread): [Python-Dev] Set program name through exec -a or environment variable
• Next message (by thread): [Python-Dev] Set program name through exec -a
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Hi!

On Sat, Mar 18, 2017 at 02:15:12PM +0100, Freddy Rietdijk <freddyrietdijk at fridh.nl> wrote:
> I would like to know if you're open to supporting `exec -a` or an

   Not everyone here knows what `exec -a` is so let me say that it's a
bashism that sets program's name. `exec prog` is interpreted as a system
call `exec('prog', 'prog')` and  `exec -a name prog` is interpreted as
`exec('prog', 'name')`.

   Currently sys.argv[0] is the name of the script and it should stay
that way. But it would be interesting to preserve argv[0] from C and
expose it via sys in addition to sys.executable. Something like
sys.original_prog_name. Then the OP can do anything application-specific
-- set sys.argv[0], call setproctitle, whatever.

> Kind regards,
> 
> Frederik

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.

---

• Previous message (by thread): [Python-Dev] Set program name through exec -a or environment variable
• Next message (by thread): [Python-Dev] Set program name through exec -a
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list