Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!eweka.nl!lightspeed.eweka.nl!194.134.4.91.MISMATCH!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Date: Fri, 14 Jun 2013 10:22:31 +0200
From: Antoon Pardon <antoon.pardon@rece.vub.ac.be>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: python-list@python.org
Subject: Re: A few questiosn about encoding
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> <mailman.3258.1371195459.3114.python-list@python.org> <kpehuv$p37$6@news.ntua.gr>
In-Reply-To: <kpehuv$p37$6@news.ntua.gr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.3266.1371198179.3114.python-list@python.org>
Lines: 59
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:48082

Op 14-06-13 09:49, Nick the Gr33k schreef:
> On 14/6/2013 10:36 πμ, Antoon Pardon wrote:
>> Op 13-06-13 10:08, Νικόλαος Κούρας schreef:
>>>
>>> Indeed python embraced it in single quoting '0b100000001011010' and
>>> not as 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?
>>
>> You don't. You should remember that python (or any programming language)
>> doesn't print numbers. It always prints string representations of
>> numbers. It is just so that we are so used to the decimal representation
>> that we think of that representation as being the number.
>>
>> Normally that is not a problem but it can cause confusion when you are
>> working with mulitple representations.
> Hold on!
> Youa re basically saying here that:
>
>
> >>> 16474
> 16474
>
> is nto a number as we think but instead is string representation of a
> number?
Yes, or if you prefer what python prints is the decimal notation of the number.  

>
> I dont think so, if it were a string representation of a number that
> would print the following:
>
> >>> 16474
> '16474'

No it wouldn't, You are confusing representation in the everyday meaning
with representation as python jargon.


> Python prints numbers:
No it doesn't, numbers are abstract concepts that can be represented in
various notations, these notations are strings. Those notaional strings
end up being printed. As I said before we are so used in using the
decimal notation that we often use the notation and the number interchangebly
without a problem. But when we are working with multiple notations that
can become confusing and we should be careful to seperate numbers from their
representaions/notations.


> but when we need a decimal integer

There are no decimal integers. There is only a decimal notation of the number.
Decimal, octal etc are not characteristics of the numbers themselves.

-- 

Antoon Pardon