➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients asvetlov, jnoller, kristjan.jonsson, loewis, ocean-city
Date 2009-04-02.14:03:30
SpamBayes Score 2.022739e-06
Marked as misclassified No
Message-id <49D4C595.5090603@v.loewis.de>
In-reply-to <1238665571.66.0.863081444621.issue5619@psf.upfronthosting.co.za>
Content 
> Since you object to a command line parameter, how about an environment 
> variable? PYTHONUNATTENDED could be used in the library startup to turn 
> off any conceivable dialogue boxes and would be passed on to child 
> processes.  This could then also easily be added in the build slave 
> config script:  sys.env[PYTHONUNATTENDED] = "1"

That would work for me. I suppose test.bat would set this variable,
right?
History
Date User Action Args
2009-04-02 14:03:33loewissetrecipients: + loewis, kristjan.jonsson, ocean-city, jnoller, asvetlov
2009-04-02 14:03:31loewislinkissue5619 messages
2009-04-02 14:03:30loewiscreate