Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder2.hal-mli.net!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <kpbul5$7bj$2@news.ntua.gr>
References: <6dfa3707-80f4-407a-a109-66dbb0130513@googlegroups.com> <mailman.2923.1370797972.3114.python-list@python.org> <kp9drh$1o0t$1@news.ntua.gr> <51b83e5a$0$29998$c3e8da3$5496439d@news.astraweb.com> <kp9lo6$9l5$2@news.ntua.gr> <51b90ead$0$29997$c3e8da3$5496439d@news.astraweb.com> <kpbnmg$qvk$2@news.ntua.gr> <51b9708b$0$29872$c3e8da3$5496439d@news.astraweb.com> <kpbt5i$7bj$1@news.ntua.gr> <mailman.3172.1371110288.3114.python-list@python.org> <kpbul5$7bj$2@news.ntua.gr>
Date: Thu, 13 Jun 2013 18:20:38 +1000
Subject: Re: A few questiosn about encoding
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.3173.1371111646.3114.python-list@python.org>
Lines: 42
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:47923

On Thu, Jun 13, 2013 at 6:08 PM, =CE=9D=CE=B9=CE=BA=CF=8C=CE=BB=CE=B1=CE=BF=
=CF=82 =CE=9A=CE=BF=CF=8D=CF=81=CE=B1=CF=82 <support@superhost.gr> wrote:
> On 13/6/2013 10:58 =CF=80=CE=BC, Chris Angelico wrote:
>>
>> On Thu, Jun 13, 2013 at 5:42 PM, =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=
=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=
=BF=BD=EF=BF=BD <support@superhost.gr>
>> wrote:
>>
>>> On 13/6/2013 10:11 =EF=BF=BD=EF=BF=BD, Steven D'Aprano wrote:
>>>>
>>>> No! That creates a string from 16474 in base two:
>>>> '0b100000001011010'
>>>
>>>
>>> I disagree here.
>>> 16474 is a number in base 10. Doing bin(16474) we get the binary
>>> representation of number 16474 and not a string.
>>> Why you say we receive a string while python presents a binary number?
>>
>>
>> You can disagree all you like. Steven cited a simple point of fact,
>> one which can be verified in any Python interpreter. Nikos, you are
>> flat wrong here; bin(16474) creates a string.
>
>
> Indeed python embraced it in single quoting '0b100000001011010' and not a=
s
> 0b100000001011010 which in fact makes it a string.
>
> But since bin(16474) seems to create a string rather than an expected
> number(at leat into my mind) then how do we get the binary representation=
 of
> the number 16474 as a number?

In Python 2:
>>> 16474

In Python 3, you have to fiddle around with ctypes, but broadly
speaking, the same thing.

ChrisA