Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.052 X-Spam-Evidence: '*H*': 0.90; '*S*': 0.00; 'subject:Python': 0.06; 'subject:help': 0.08; 'subject:modules': 0.09; 'cc:addr:python- list': 0.11; '23,': 0.16; 'seconds,': 0.16; 'seconds.': 0.16; 'wrote:': 0.18; 'received:10.0.1': 0.19; 'split': 0.19; 'feb': 0.22; 'cc:addr:python.org': 0.22; 'hours,': 0.24; 'cc:2**0': 0.24; 'purposes': 0.26; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; '[1]': 0.29; 'unix': 0.29; "i'm": 0.30; 'went': 0.31; 'code': 0.31; 'weeks': 0.32; "we're": 0.32; 'subject:with': 0.35; 'but': 0.35; 'minutes,': 0.36; 'method': 0.36; 'thanks': 0.36; 'possible': 0.36; 'received:10.0': 0.36; 'similar': 0.36; 'seconds': 0.37; 'received:10': 0.37; 'pm,': 0.38; 'how': 0.40; 'header:Message-Id:1': 0.63; 'field': 0.63; 'to:addr:gmail.com': 0.65; 'charset:windows-1252': 0.65; 'minutes': 0.67; '2014,': 0.84; 'exercise,': 0.84; 'happened.': 0.84; 'scott': 0.93 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A02020A.52F6DDE4.0060,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=E9kTU9hl c=1 sm=1 a=MB85R812cvcrhCHz/P2OVA==:17 a=IwL8z8QTeS0A:10 a=G8Uczd0VNMoA:10 a=N659UExz7-8A:10 a=kviXuzpPAAAA:8 a=_HE405UYfI8A:10 a=pGLkceISAAAA:8 a=WOBzA-oE1bByXAMGMLIA:9 a=pILNOxqGKmIA:10 a=MSl-tDqOz04A:10 a=ad59HFDvWhEeDpEJ:21 a=ZS3DVWXechxTfbXt:21 a=MB85R812cvcrhCHz/P2OVA==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; auth=pass (PLAIN) smtp.auth=swdunning@cox.net Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: Python 2.7.6 help with modules From: Scott W Dunning In-Reply-To: Date: Sat, 8 Feb 2014 18:46:11 -0700 Content-Transfer-Encoding: quoted-printable References: <032F2E23-6983-4710-B087-C1771B66C3EF@cox.net> <635C857D-1F7A-4F95-B3A7-F1A3C69BF137@cox.net> <07C379F9-3BD4-4DC4-8FEF-BA3B0067A7B1@cox.net> To: Chris Angelico X-Mailer: Apple Mail (2.1827) Cc: "python-list@python.org" X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 28 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1391910375 news.xs4all.nl 2942 [2001:888:2000:d::a6]:43444 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:65703 On Feb 8, 2014, at 5:56 PM, Chris Angelico wrote: >=20 > 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 = same 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)?=20 > [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=92ll take your word = for it. lol Thanks again!!! Scott