On Fri, 19 Aug 2022 at 10:07, Grant Edwards wrote:
>
> On 2022-08-18, Chris Angelico wrote:
> > On Fri, 19 Aug 2022 at 05:05, Grant Edwards
> > wrote:
> >> On 2022-08-18, Chris Angelico wrote:
> >>
> >> > It's one of the frustrations with JSON, since that format doesn't
> >> > allow the
On Tue, Aug 16, 2022 at 2:03 PM Dan Stromberg wrote:
> Hi folks.
>
> I'm attempting to package up a python package that uses Cython.
>
> Rather than build binaries for everything under the sun, I've been
> focusing on including the .pyx file and running cython on it at install
> time. This
On 2022-08-18, Chris Angelico wrote:
> On Fri, 19 Aug 2022 at 05:05, Grant Edwards wrote:
>> On 2022-08-18, Chris Angelico wrote:
>>
>> > It's one of the frustrations with JSON, since that format doesn't
>> > allow the trailing comma :)
>>
>> Yep, that's a constant, low-level pain for all the C
Hope you had a good time.
On Wed, Aug 17, 2022 at 10:19 PM Peter J. Holzer wrote:
> On 2022-08-17 12:09:14 -0600, David at Booomer wrote:
> > Executable(
> >
> "prjui.py","Maiui.py","about.py","dict.py","geometry.py","getEquation.py",
> >
>
On Fri, 19 Aug 2022 at 08:15, Tobiah wrote:
>
> > You configure the web server to send:
> >
> > Content-Type: text/html; charset=...
> >
> > in the HTTP header when it serves HTML files.
>
> So how does this break down? When a person enters
> Montréal, Quebéc into a form field, what are
On 2022-08-18, Tobiah wrote:
>> You configure the web server to send:
>>
>> Content-Type: text/html; charset=...
>>
>> in the HTTP header when it serves HTML files.
>
> So how does this break down? When a person enters
> Montréal, Quebéc into a form field, what are they
> doing on the
You configure the web server to send:
Content-Type: text/html; charset=...
in the HTTP header when it serves HTML files.
So how does this break down? When a person enters
Montréal, Quebéc into a form field, what are they
doing on the keyboard to make that happen? As the
string sits
On Fri, 19 Aug 2022 at 05:05, Grant Edwards wrote:
>
> On 2022-08-18, Chris Angelico wrote:
> > On Fri, 19 Aug 2022 at 04:19, David at Booomer wrote:
> >
> >> The trailing , does make commenting out arguments easier but
> >> unexpected coming from ‘older’ languages. ;-)
> >
> > It's one of the
On 2022-08-18, Chris Angelico wrote:
> On Fri, 19 Aug 2022 at 04:19, David at Booomer wrote:
>
>> The trailing , does make commenting out arguments easier but
>> unexpected coming from ‘older’ languages. ;-)
>
> It's one of the frustrations with JSON, since that format doesn't
> allow the
On 2022-08-18, Tobiah wrote:
>> Generally speaking browser submisisons were/are supposed to be sent
>> using the same encoding as the page, so if you're sending the page
>> as "latin1" then you'll see that a fair amount I should think. If you
>> send it as "utf-8" then you'll get 100% utf-8 back.
On Fri, 19 Aug 2022 at 04:19, David at Booomer wrote:
> > This is really common in modern programming languages (read: programming
> > languages younger than 30 years or so), because it makes it much more
> > convenient to extend/shorten/reorder a list. Otherwise you alway have to
> > remember
From: Dennis Lee Bieber
>
> On Wed, 17 Aug 2022 12:09:14 -0600, David at Booomer
> declaimed the following:
>
>> executables=[
>> Executable(
>>
>> "prjui.py","Maiui.py","about.py","dict.py","geometry.py","getEquation.py",
>>
>>
On 2022-08-17, Barry wrote:
>> On 17 Aug 2022, at 18:30, Jon Ribbens via Python-list
>> wrote:
>> On 2022-08-17, Tobiah wrote:
>>> I get data from various sources; client emails, spreadsheets, and
>>> data from web applications. I find that I can do
>>> some_string.decode('latin1')
>>> to
Generally speaking browser submisisons were/are supposed to be sent
using the same encoding as the page, so if you're sending the page
as "latin1" then you'll see that a fair amount I should think. If you
send it as "utf-8" then you'll get 100% utf-8 back.
The only trick I know is to use .
On 2022-08-17, Tobiah wrote:
>> That has already been decided, as much as it ever can be. UTF-8 is
>> essentially always the correct encoding to use on output, and almost
>> always the correct encoding to assume on input absent any explicit
>> indication of another encoding. (e.g. the HTML
15 matches
Mail list logo
