Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #64944 > unrolled thread

pytz question: GMT vs. UTC

Back to article view | Back to comp.lang.python

Contents

  pytz question: GMT vs. UTC Skip Montanaro <skip@pobox.com> - 2014-01-29 11:29 -0600
    Re: pytz question: GMT vs. UTC Grant Edwards <invalid@invalid.invalid> - 2014-01-29 19:02 +0000
      Re: pytz question: GMT vs. UTC Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-01-29 19:17 -0500
      Re: pytz question: GMT vs. UTC Chris Angelico <rosuav@gmail.com> - 2014-01-30 11:28 +1100
      Re: pytz question: GMT vs. UTC Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-01-29 20:50 -0500
      Re: pytz question: GMT vs. UTC MRAB <python@mrabarnett.plus.com> - 2014-01-30 02:40 +0000
      Re: pytz question: GMT vs. UTC Chris Angelico <rosuav@gmail.com> - 2014-01-30 14:27 +1100
        Re: pytz question: GMT vs. UTC wxjmfauth@gmail.com - 2014-01-30 00:45 -0800
          Re: pytz question: GMT vs. UTC MRAB <python@mrabarnett.plus.com> - 2014-01-30 11:51 +0000
          Re: pytz question: GMT vs. UTC Grant Edwards <invalid@invalid.invalid> - 2014-01-30 15:21 +0000
            Re: pytz question: GMT vs. UTC Dan Sommers <dan@tombstonezero.net> - 2014-01-31 04:08 +0000
              Re: pytz question: GMT vs. UTC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-01-31 04:37 +0000
                Re: pytz question: GMT vs. UTC Dan Sommers <dan@tombstonezero.net> - 2014-01-31 06:28 +0000
                  Re: pytz question: GMT vs. UTC Chris Angelico <rosuav@gmail.com> - 2014-01-31 17:42 +1100
                    Re: pytz question: GMT vs. UTC Dan Sommers <dan@tombstonezero.net> - 2014-02-01 06:30 +0000
                Re: pytz question: GMT vs. UTC Roy Smith <roy@panix.com> - 2014-01-31 10:00 -0500
              Re: pytz question: GMT vs. UTC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-01-31 09:59 +0000
            Re: pytz question: GMT vs. UTC Pete Forman <petef4+usenet@gmail.com> - 2014-02-02 12:45 +0000
              Re: pytz question: GMT vs. UTC wxjmfauth@gmail.com - 2014-02-02 06:38 -0800
              Re: pytz question: GMT vs. UTC Grant Edwards <invalid@invalid.invalid> - 2014-02-02 16:03 +0000
          Re: pytz question: GMT vs. UTC Rustom Mody <rustompmody@gmail.com> - 2014-01-30 23:02 -0800
            Re: pytz question: GMT vs. UTC wxjmfauth@gmail.com - 2014-01-31 02:17 -0800
              Re: pytz question: GMT vs. UTC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-01-31 14:50 +0000
                Re: pytz question: GMT vs. UTC Roy Smith <roy@panix.com> - 2014-01-31 10:04 -0500
                  Re: pytz question: GMT vs. UTC Robert Kern <robert.kern@gmail.com> - 2014-01-31 15:08 +0000
      Re: pytz question: GMT vs. UTC Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-01-30 19:44 +1300
      Re: pytz question: GMT vs. UTC Christian Heimes <christian@python.org> - 2014-01-30 10:49 +0100
        Re: pytz question: GMT vs. UTC wxjmfauth@gmail.com - 2014-01-30 02:10 -0800
        Re: pytz question: GMT vs. UTC Grant Edwards <invalid@invalid.invalid> - 2014-01-30 15:23 +0000
          Re: pytz question: GMT vs. UTC Larry Martell <larry.martell@gmail.com> - 2014-01-30 10:28 -0500
      Re: pytz question: GMT vs. UTC Chris Angelico <rosuav@gmail.com> - 2014-01-30 21:10 +1100
      Re: pytz question: GMT vs. UTC Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-01-30 20:18 -0500

Page 2 of 2 — ← Prev page 1 [2]

#65103

On Thursday, January 30, 2014 2:15:20 PM UTC+5:30, jmf wrote:
> Le jeudi 30 janvier 2014 04:27:54 UTC+1, Chris Angelico a écrit :
> > On Thu, Jan 30, 2014 at 1:40 PM, MRAB  wrote:
> > >>         How cruel... I suspect the smack at 0degC is much more painful
> > >> than one
> > > It's the 21st century; you should be making use of Unicode: 0°C.
> > I started to read that and thought you were going to advocate the use of 0°K...

> ======

> The temperature unit is the "Kelvin", not the "Degree Kelvin".
> One writes: 0 K, 275.15 K

OMG! OMG!!
That is an ASCII K and not a unicode K

Now poor jmf will suffer the fire and brimstone of hell without
diacrïticál marks

[toc] | [prev] | [next] | [standalone]

#65109

Le vendredi 31 janvier 2014 08:02:22 UTC+1, Rustom Mody a écrit :
> On Thursday, January 30, 2014 2:15:20 PM UTC+5:30, jmf wrote:
> 
> > Le jeudi 30 janvier 2014 04:27:54 UTC+1, Chris Angelico a écrit :
> 
> > > On Thu, Jan 30, 2014 at 1:40 PM, MRAB  wrote:
> 
> > > >>         How cruel... I suspect the smack at 0degC is much more painful
> 
> > > >> than one
> 
> > > > It's the 21st century; you should be making use of Unicode: 0°C.
> 
> > > I started to read that and thought you were going to advocate the use of 0°K...
> 
> 
> 
> > ======
> 
> 
> 
> > The temperature unit is the "Kelvin", not the "Degree Kelvin".
> 
> > One writes: 0 K, 275.15 K
> 
> 
> 
> OMG! OMG!!
> 
> That is an ASCII K and not a unicode K
> 
> 
> 
> Now poor jmf will suffer the fire and brimstone of hell without
> 
> diacrïticál marks

====

I'm aware of what I did.

1) You wrote: "That is an ASCII K and not a unicode K".

This is a non sense. You are opposing ascii and unicode,
the reperoire of the ascii chars and the repertoire of the
Unicode chars.

In unicode, the are two "K"'s, one for the letter and one
for the Kelvin unit, see my previous post.

2) I used the letter "K" for commodity. Btw, I'm also
aware the 'KELVIN SIGN' is not availaible in many fonts.

3) If you wish to discuss the typographical aspect
in that story, one can discuss the kind of space which
should separate the number and the unit ('SPACE',
'SOFT HYPHEN', 'NARROW NO-BREAK SPACE',
'HAIR SPACE', ...). My "lazy" white space can also be
considered as a mistake.

4) What is definitively wrong is to claim :

"It's the 21st century; you should be making use of
Unicode: 0°C."

The 'DEGREE SIGN' and "Unicode" are two different
things. It exists in many coding schemes.


cs = ['iso-8859-1', 'iso-8859-2', 'cp437', 'cp850', 'cp1252', 'cp857',\
    'iso-8859-15']
for c in cs:
    c, '\u00b0'.encode(c, 'replace').decode(c)
    
>>> cs = ['iso-8859-1', 'iso-8859-2', 'cp437', 'cp850', 'cp1252', 'cp857',\
...     'iso-8859-15']
>>> for c in cs:
...     c, '\u00b0'.encode(c, 'replace').decode(c)
...     
('iso-8859-1', '°')
('iso-8859-2', '°')
('cp437', '°')
('cp850', '°')
('cp1252', '°')
('cp857', '°')
('iso-8859-15', '°')
>>>

5) Not unicode. The "°" is available as "direct (Shift) key"
on many European keyboards.

6) Finally and for the record : "n Kelvin" and not "n Degree Kelvin".

jmf

[toc] | [prev] | [next] | [standalone]

#65122

On 31/01/2014 10:17, wxjmfauth@gmail.com wrote:

Is the double line spacing that you still use despite being asked not to 
ASCII or unicode?

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

[toc] | [prev] | [next] | [standalone]

#65125

In article <mailman.6209.1391180106.18130.python-list@python.org>,
 Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:

> On 31/01/2014 10:17, wxjmfauth@gmail.com wrote:
> 
> Is the double line spacing that you still use despite being asked not to 
> ASCII or unicode?

It's not actually double line spacing.  It's single spaced using UNICODE 
DOUBLE COMBINING LINEFEED WITH QUOTE MARKER as line terminators.

[toc] | [prev] | [next] | [standalone]

#65127

On 2014-01-31 15:04, Roy Smith wrote:
> In article <mailman.6209.1391180106.18130.python-list@python.org>,
>   Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:
>
>> On 31/01/2014 10:17, wxjmfauth@gmail.com wrote:
>>
>> Is the double line spacing that you still use despite being asked not to
>> ASCII or unicode?
>
> It's not actually double line spacing.  It's single spaced using UNICODE
> DOUBLE COMBINING LINEFEED WITH QUOTE MARKER as line terminators.

 >>> len('\n\n>')
3

Clearly, the FSR is broken beyond repair.

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
  that is made terrible by our own mad attempt to interpret it as though it had
  an underlying truth."
   -- Umberto Eco

[toc] | [prev] | [next] | [standalone]

#64970

Grant Edwards wrote:

> smacked across the knuckes with a 12-inch platinum-iridium ruler

Imperial or Scottish inches?

-- 
Greg

[toc] | [prev] | [next] | [standalone]

#64975

On 30.01.2014 04:27, Chris Angelico wrote:
> On Thu, Jan 30, 2014 at 1:40 PM, MRAB <python@mrabarnett.plus.com> wrote:
>>>         How cruel... I suspect the smack at 0degC is much more painful
>>> than one
>>> at room temperature <G>
>>>
>> It's the 21st century; you should be making use of Unicode: 0°C.
> 
> I started to read that and thought you were going to advocate the use of 0°K...

It's 0 K. The SI-unit 'Kelvin' has no degree (although Lord Kelvin was a
professor). *g*

[toc] | [prev] | [next] | [standalone]

#64976

Le jeudi 30 janvier 2014 10:49:11 UTC+1, Christian Heimes a écrit :
> On 30.01.2014 04:27, Chris Angelico wrote:
> 
> > On Thu, Jan 30, 2014 at 1:40 PM, MRAB <python@mrabarnett.plus.com> wrote:
> 
> >>>         How cruel... I suspect the smack at 0degC is much more painful
> 
> >>> than one
> 
> >>> at room temperature <G>
> 
> >>>
> 
> >> It's the 21st century; you should be making use of Unicode: 0°C.
> 
> > 
> 
> > I started to read that and thought you were going to advocate the use of 0°K...
> 
> 
> 
> It's 0 K. The SI-unit 'Kelvin' has no degree (although Lord Kelvin was a
> 
> professor). *g*


Glad, that you read (received?) my previous post!

[toc] | [prev] | [next] | [standalone]

#65021

On 2014-01-30, Christian Heimes <christian@python.org> wrote:
> On 30.01.2014 04:27, Chris Angelico wrote:
>> On Thu, Jan 30, 2014 at 1:40 PM, MRAB <python@mrabarnett.plus.com> wrote:
>>>>         How cruel... I suspect the smack at 0degC is much more painful
>>>> than one
>>>> at room temperature <G>
>>>>
>>> It's the 21st century; you should be making use of Unicode: 0??C.
>> 
>> I started to read that and thought you were going to advocate the use of 0??K...
>
> It's 0 K. The SI-unit 'Kelvin' has no degree (although Lord Kelvin was a
> professor).

And he did have a degree.

-- 
Grant Edwards               grant.b.edwards        Yow! Wait ... is this a FUN
                                  at               THING or the END of LIFE in
                              gmail.com            Petticoat Junction??

[toc] | [prev] | [next] | [standalone]

#65022

On Thu, Jan 30, 2014 at 10:23 AM, Grant Edwards <invalid@invalid.invalid> wrote:
> On 2014-01-30, Christian Heimes <christian@python.org> wrote:
>> On 30.01.2014 04:27, Chris Angelico wrote:
>>> On Thu, Jan 30, 2014 at 1:40 PM, MRAB <python@mrabarnett.plus.com> wrote:
>>>>>         How cruel... I suspect the smack at 0degC is much more painful
>>>>> than one
>>>>> at room temperature <G>
>>>>>
>>>> It's the 21st century; you should be making use of Unicode: 0??C.
>>>
>>> I started to read that and thought you were going to advocate the use of 0??K...
>>
>> It's 0 K. The SI-unit 'Kelvin' has no degree (although Lord Kelvin was a
>> professor).
>
> And he did have a degree.

I heard he was a very cold individual.

[toc] | [prev] | [next] | [standalone]

#64977

On Thu, Jan 30, 2014 at 8:49 PM, Christian Heimes <christian@python.org> wrote:
> On 30.01.2014 04:27, Chris Angelico wrote:
>> On Thu, Jan 30, 2014 at 1:40 PM, MRAB <python@mrabarnett.plus.com> wrote:
>>>>         How cruel... I suspect the smack at 0degC is much more painful
>>>> than one
>>>> at room temperature <G>
>>>>
>>> It's the 21st century; you should be making use of Unicode: 0°C.
>>
>> I started to read that and thought you were going to advocate the use of 0°K...
>
> It's 0 K. The SI-unit 'Kelvin' has no degree (although Lord Kelvin was a
> professor). *g*

That thing.  I knew that, honest I did. My brain's just not working
properly at the moment, something to do with consecutive hours awake.
But later on I'll be 0K.

ChrisA

[toc] | [prev] | [next] | [standalone]

#65076

On Thu, 30 Jan 2014 14:27:54 +1100, Chris Angelico <rosuav@gmail.com>
declaimed the following:

>On Thu, Jan 30, 2014 at 1:40 PM, MRAB <python@mrabarnett.plus.com> wrote:
>>>         How cruel... I suspect the smack at 0degC is much more painful
>>> than one
>>> at room temperature <G>
>>>
>> It's the 21st century; you should be making use of Unicode: 0°C.
>
>I started to read that and thought you were going to advocate the use of 0°K...
>
	Never! Rankine all the way
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.python

csiph-web