On Sat, Mar 18, 2017 at 10:27:58AM -0500, Ryan Gonzalez <rym...@gmail.com> wrote: > exec -a would seem to end up setting argv[0] on the CPython interpreter > itself, which I don't think is the desired effect...
That's exactly what OP asked -- how to change that? > -- > Ryan (????????????) > Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else > http://refi64.com > > On Mar 18, 2017 10:11 AM, "Freddy Rietdijk" <freddyrietd...@fridh.nl> wrote: > > I would like to know if you're open to supporting `exec -a` or an > > environment variable for setting `argv[0]`, and have some pointers as to > > where that should be implemented. > > > > On Nixpkgs we typically use wrappers to set environment variables like > > PATH or PYTHONPATH for individual programs. Consider a program named > > `prog`. We move the original program `prog` to `.prog-wrapped` and then > > create a wrapper `prog` that does `exec -a prog .prog-wrapped`. > > > > Unfortunately `exec -a` does not work with Python. The process is still > > named `.prog-wrapped` (although that's not really a problem) but worse, > > `sys.argv[0]` is also `.prog-wrapped`. Currently we inject some code in > > programs that sets `sys.argv=[0] = "prog" but this is fragile and I would > > prefer to get rid of this. > > > > Kind regards, > > > > Frederik Oleg. -- Oleg Broytman http://phdru.name/ p...@phdru.name Programmers don't die, they just GOSUB without RETURN. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
