On Fri, 2010-07-16 at 23:38 -0500, Ian Bicking wrote:
> On Fri, Jul 16, 2010 at 9:43 PM, Chris McDonough
> wrote:
>
> > Nah, not nearly that hard:
> >
> > path_info =
> >
>
> urllib.parse.unquote_to_bytes(environ['wsgi.raw_path_info']).decode('UTF-
On 17 July 2010 22:30, wrote:
> On Fri, 16 Jul 2010, P.J. Eby wrote:
>
>> At 02:28 PM 7/16/2010 -0500, Ian Bicking wrote:
>> There should be one, and preferably *only* one, obvious way to do it.
>>
>> And given that HTTP is inherently a bunch of bytes, bytes is the one
>> obvious way.
>
> I think
On Sat, Jul 17, 2010 at 5:57 AM, Armin Ronacher wrote:
> On 7/17/10 9:15 AM, Ian Bicking wrote:
>
>> This is an Apache-specific issue. It definitely doesn't apply to
>> paste.httpserver, I doubt CherryPy or wsgiref. I don't really know how
>> Nginx or other servers work.
>>
>
> This will be an
Chris McDonough wrote:
> On Sat, 2010-07-17 at 01:33 +0200, Armin Ronacher wrote:
> > Hi,
> >
> > On 7/17/10 1:20 AM, Chris McDonough wrote:
> > > Let me know if I'm missing something.
> > The only thing you miss is that the bytes type of Python 3 is badly
> > supported in the stdlib (not an i
On 17-07-2010, chris.d...@gmail.com wrote:
> On Fri, 16 Jul 2010, P.J. Eby wrote:
>
>> At 02:28 PM 7/16/2010 -0500, Ian Bicking wrote:
>> There should be one, and preferably *only* one, obvious way to do it.
>>
>> And given that HTTP is inherently a bunch of bytes, bytes is the one obvious
>> way.
[PJ Eby]
> IOW, the bytes/string discussion on Python-dev has kind of led me to realize
> that we might just as well make the *entire* stack bytes (incoming and
> outgoing headers *and* streams), and rewrite that bit in PEP 333 about using
> str on "Python 3000" to say we go with bytes on Python 3+
On Fri, 16 Jul 2010, P.J. Eby wrote:
At 02:28 PM 7/16/2010 -0500, Ian Bicking wrote:
There should be one, and preferably *only* one, obvious way to do it.
And given that HTTP is inherently a bunch of bytes, bytes is the one obvious
way.
I think this makes sense. The thing which is assembling
On Saturday, July 17, 2010, Antoine Pitrou wrote:
> Ian Bicking writes:
>>
>> So... there's been some discussion of WSGI on Python 3 lately.
>> I'm not feeling as pessimistic as some people, I feel like we were close
>> but just didn't *quite* get there.
>> Here's my thoughts:
>> * Everyone agree
Ian Bicking writes:
>
> So... there's been some discussion of WSGI on Python 3 lately.
> I'm not feeling as pessimistic as some people, I feel like we were close
> but just didn't *quite* get there.
> Here's my thoughts:
> * Everyone agrees keys in the environ should be native strings
I don't kn
Hi,
On 7/17/10 12:57 PM, Armin Ronacher wrote:
In fact, this will be an issue for things like middlewares that want to
map applications to paths. In fact, this already is an issue on Python 2
already, just that nobody cares.
s/applications/serving static files from folders/
Regards,
Armin
___
Hi,
On 7/17/10 9:15 AM, Ian Bicking wrote:
This is an Apache-specific issue. It definitely doesn't apply to
paste.httpserver, I doubt CherryPy or wsgiref. I don't really know how
Nginx or other servers work.
This will be an issue for every server that...
* supports unicode filesystems
* de
On Saturday, July 17, 2010, Ian Bicking wrote:
> On Sat, Jul 17, 2010 at 12:38 AM, Graham Dumpleton
> wrote:
>
>
> On Friday, July 16, 2010, And Clover wrote:
>> On 07/14/2010 06:43 AM, Ian Bicking wrote:
>>
>>
>> There's only a couple tricky keys: SCRIPT_NAME, PATH_INFO,
>> and HTTP_COOKIE.
>>
On Sat, Jul 17, 2010 at 12:38 AM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:
> On Friday, July 16, 2010, And Clover wrote:
> > On 07/14/2010 06:43 AM, Ian Bicking wrote:
> >
> >
> > There's only a couple tricky keys: SCRIPT_NAME, PATH_INFO,
> > and HTTP_COOKIE.
> >
> >
> > (And of thos
13 matches
Mail list logo
