[Python-ideas] Updated PEP 432: Simplifying the CPython update sequence (original) (raw)
Victor Stinner victor.stinner at gmail.com
Sun Jan 13 01:43:55 CET 2013
- Previous message: [Python-ideas] Updated PEP 432: Simplifying the CPython update sequence
- Next message: [Python-ideas] Updated PEP 432: Simplifying the CPython update sequence
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2013/1/13 Daniel Shahaf <d.s at daniel.shahaf.name>:
Quick question, do you plan to expose the C argv values as part of this work?
Issue #14208 asks for the full C argv array; my use-case today required only the C argv[0]. Both of the use-cases had to do with having a script reexecute itself (eg, 'os.execl(sys.executable, *args)').
I don't remember where, but it was already asked how is it possible to recreate the Python command line to create a subprocess with the Python command line options.
For example:
$ python -O -c "import sys; print(sys.argv)" ['-c']
How do you get ['python', '-O']? I guess that the question was for the multiprocessing on Windows (which does not support fork).
Victor
- Previous message: [Python-ideas] Updated PEP 432: Simplifying the CPython update sequence
- Next message: [Python-ideas] Updated PEP 432: Simplifying the CPython update sequence
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]