opensubscriber
   Find in this group all groups
 
Unknown more information…

w : web-sig@python.org 8 January 2011 • 8:56AM -0500

Re: [Web-SIG] Declaring PEP 3333 accepted (was: PEP 444 != WSGI 2.0)
by Graham Dumpleton

REPLY TO AUTHOR
 
REPLY TO GROUP




On 8 January 2011 02:55, P.J. Eby <pje@tele...> wrote:
> At 05:27 PM 1/7/2011 +1100, Graham Dumpleton wrote:
>>
>> Another thing though. For output changed to sys.stdout.buffer. For
>> input should we be using sys.stdin.buffer as well if want bytes?
>
> %&$*()&%!!!  Sorry, still getting used to this whole Python 3 thing.
>  (Honestly, I don't even use Python 2.6 for anything real yet.)
>
>
>> Good thing I tried running this. Did we all assume that someone else
>> was actually running it to check it? :-)
>
> Well, I only recently started changing the examples to actual Python 3, vs
> being the old Python 2 examples.  Though, I'm not sure anybody ever ran the
> Python 2 ones.  ;-)

Latest CGI/WSGI bridge example extract from PEP 3333 seems to work
okay for my simple test.

So, if no more technical problems (vs cosmetic) that anyone else sees,
that is probably it and and we can toss this baby out the door.

Graham
_______________________________________________
Web-SIG mailing list
Web-SIG@pyth...
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe: http://mail.python.org/mailman/options/web-sig/subscriber%40opensubscriber.com

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.