On 11/21/2010 8:39 PM, R. David Murray wrote:
On Sun, 21 Nov 2010 19:59:54 -0800, Glenn Linderman
wrote:
On 11/21/2010 9:18 AM, R. David Murray wrote:
I want to look at the CGI issue, but I'm not sure when I'll get to it.
Actually, since this code was working before 3.x, and if email.parser
On Sun, 21 Nov 2010 19:59:54 -0800, Glenn Linderman
wrote:
> On 11/21/2010 9:18 AM, R. David Murray wrote:
> > I want to look at the CGI issue, but I'm not sure when I'll get to it.
>
> Actually, since this code was working before 3.x, and if email.parser
> can now accept binary streams, it see
On 11/21/2010 9:18 AM, R. David Murray wrote:
I want to look at the CGI issue, but I'm not sure when I'll get to it.
Actually, since this code was working before 3.x, and if email.parser
can now accept binary streams, it seems like maybe the only thing that
might be wrong is that presently it
On Sat, 20 Nov 2010 23:52:45 -0800, Glenn Linderman
wrote:
> Sadly, cgi.py input handling seems to depend on the email module,
> thought to be fixed for 3.2, but it is not clear if that has been
> achieved, or if the surrogate encode workaround is sufficient for this.
> More testing needed, b
On 11/20/2010 10:19 AM, Glenn Linderman wrote:
Oops. Yes, that fixes the problem with creation of the temp file,
thanks for catching that. I now get a complete report of the
original error in the temp file (below). I am a bit less confused
now... but it seems that there are still a number o
On 11/20/2010 3:38 AM, Éric Araujo wrote:
Hello
cgitb.enable(0,"d:\temp")
Isn’t that expanded to “d:emp”?
Oops. Yes, that fixes the problem with creation of the temp file,
thanks for catching that. I now get a complete report of the original
error in the temp file (below). I am a bit
Hello
> cgitb.enable(0,"d:\temp")
Isn’t that expanded to “d:emp”?
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive
On 11/19/2010 7:48 PM, Glenn Linderman wrote:
One of the cgitb outputs from my attempt to serve the binary file
claims that my CGI script's output file (which comes from a subprocess
PIPE) is a TextIOWrapper with encoding cp1252. Maybe that is the
default that comes when a new Python is launch
So maybe this is the wrong forum, if so please tell me what the right
forum is for each of the various pieces. I'm assuming that I should
file some bugs in the tracker, but I'm not exactly sure whether to file
them on cgitb, http.server, or subprocess, or all of the above. Pretty
sure there a
