Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <8C13948E-1A2A-4221-89D3-C117B4A10F78@cox.net>
References: <032F2E23-6983-4710-B087-C1771B66C3EF@cox.net> <635C857D-1F7A-4F95-B3A7-F1A3C69BF137@cox.net> <07C379F9-3BD4-4DC4-8FEF-BA3B0067A7B1@cox.net> <8C13948E-1A2A-4221-89D3-C117B4A10F78@cox.net>
Date: Sun, 9 Feb 2014 12:50:01 +1100
Subject: Re: Python 2.7.6 help with modules
From: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <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.6556.1391910605.18130.python-list@python.org>
Lines: 40
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:65705

On Sun, Feb 9, 2014 at 12:46 PM, Scott W Dunning <swdunning@cox.net> wrote:
> On Feb 8, 2014, at 5:56 PM, Chris Angelico <rosuav@gmail.com> wrote:
>>
>> Carry on with that method - work out the number of minutes, and then
>> the "hours_etc" which has the rest. Then do the same to split off
>> hours, and then days. See how you go!
>
> I did it similar to that but I went backwards.  I started with number of =
weeks and went down to seconds remaining.  Would the result still be the sa=
me if the order of the code went the other way (i.e.. from minutes to weeks=
 instead of the way I did it from weeks to seconds)?
>

The result will be the same. You can work either way. Working from the
smallest up lets you work in different formats - maybe you want to
suppress "0 weeks, 0 days" if it's less than a day, for instance.
Working from the largest down means you can simply write things out as
you get them, and they'll be in the right order for a human to read
(look back up to my aside where I show assembly-language number
display, and you'll see that the digits come out in the wrong order).

>> [1] For the purposes of this exercise, I'm pretending that this is
>> Unix time and has no leap seconds. Technically, when you write out
>> HH:MM:SS, the HH field can go from 00 to 23, the MM field can go from
>> 00 to 59, and the SS field can go from 00 to 61 - yes, it's possible
>> to have *two* consecutive leap seconds, although this has never yet
>> happened. But for this, we're working in a system that has seconds
>> going from 00 to 59
>
>
> I honestly do not know what leap seconds are but I=E2=80=99ll take your w=
ord for it.  lol

Heh. I mentioned them for completeness only. Look 'em up on Wikipedia
if you like; some years are a smidge longer than 365 or 366 days, by
either one or two seconds. Almost NEVER significant to every-day work,
but you'll see some time formatting libraries that mention them
(mainly because the SS field can go up to 61).

ChrisA