On Tue, May 29, 2018 at 8:39 PM, Steven D'Aprano
wrote:
> On Tue, 29 May 2018 09:19:52 +, Fabien LUCE wrote:
>
>> May 29 2018 11:12 AM, "Thomas Jollans" wrote:
>>> On 2018-05-29 09:55, f...@lutix.org wrote:
>>>
Hello,
Using Python 2.7 (will switch to Py3 soon but Before I'd like to
On Tue, 29 May 2018 09:19:52 +, Fabien LUCE wrote:
> May 29 2018 11:12 AM, "Thomas Jollans" wrote:
>> On 2018-05-29 09:55, f...@lutix.org wrote:
>>
>>> Hello,
>>> Using Python 2.7 (will switch to Py3 soon but Before I'd like to
>>> understand how string encoding worked)
>>
>> Oh dear. This
On Tue, May 29, 2018 at 5:55 PM, wrote:
> Hello,
> Using Python 2.7 (will switch to Py3 soon but Before I'd like to understand
> how string encoding worked)
> Could you please tell me is I understood well what occurs in Python's mind:
> in a .py file:
> if I write s="héhéhé", if my file is decla
May 29 2018 11:12 AM, "Thomas Jollans" wrote:
> On 2018-05-29 09:55, f...@lutix.org wrote:
>
>> Hello,
>> Using Python 2.7 (will switch to Py3 soon but Before I'd like to understand
>> how string encoding
>> worked)
>
> Oh dear. This is probably the exact wrong way to go about it: the
> interpl
On 2018-05-29 09:55, f...@lutix.org wrote:
> Hello,
> Using Python 2.7 (will switch to Py3 soon but Before I'd like to understand
> how string encoding worked)
Oh dear. This is probably the exact wrong way to go about it: the
interplay between string encoding, unicode and bytes is much less clear
