Re: [Python-Dev] Using environment variables problematic for embedded python.

2012-10-04 Thread Campbell Barton
Checked Python 3.4 (latest hg checkout) and this area of the code hasn't changed: pythonrun,c initstdio() reported the issue: http://bugs.python.org/issue16129 On Thu, Oct 4, 2012 at 2:51 PM, Guido van Rossum wrote: > This seems more fit for the tracker; can you file there? (Then post the > issu

Re: [Python-Dev] Using environment variables problematic for embedded python.

2012-10-03 Thread Guido van Rossum
This seems more fit for the tracker; can you file there? (Then post the issue link here.) I do think you have a legitimate use case to set the default encoding to utf-8. (Though there may be a way already.) Does Python 3.3 have te same bug? On Wednesday, October 3, 2012, Campbell Barton wrote: >

Re: [Python-Dev] Using environment variables problematic for embedded python.

2012-10-03 Thread Campbell Barton
On Thu, Oct 4, 2012 at 1:35 PM, Campbell Barton wrote: > Hi, > > We've run into an issue recently with blender3d on ms-windows where we > want to enforce the encoding is UTF-8 with the embedded python > interpreter. > (the encoding defaults to cp437). > > I naively thought setting the environment

[Python-Dev] Using environment variables problematic for embedded python.

2012-10-03 Thread Campbell Barton
Hi, We've run into an issue recently with blender3d on ms-windows where we want to enforce the encoding is UTF-8 with the embedded python interpreter. (the encoding defaults to cp437). I naively thought setting the environment variable before calling Py_Initialize() would work, but the way python