Re: Issue with continous incrementing of unbroken sequence for a entire working day

References	<CAJ2vgs6zZpHC_p=SuE7QWf7NDvokMjmE1N-aEN3a6n_DXi2=aQ@mail.gmail.com> <CAJ2vgs59t2fkV_T-Kdcb5Mzsr5Q8M8z4P6NwMOftg-Y5zVR8wA@mail.gmail.com>
Date	2013-03-01 18:59 +1100
Subject	Re: Issue with continous incrementing of unbroken sequence for a entire working day
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.2706.1362124759.2939.python-list@python.org> (permalink)

Show all headers | View raw

On Fri, Mar 1, 2013 at 6:50 PM, Morten Engvoldsen <mortenengv@gmail.com> wrote:
> Hi,
> No i don't want user to blame when date is changed and serial number
> reset when it should not. Do you think the following function will
> help for this:
>
> import datetime as dt
>>>> import pytz
>>>> utc = pytz.timezone("UTC")
>>>> norway = pytz.timezone("Europe/Norway")
>>>> a = dt.datetime(2008, 7, 6, 5, 4, 3, tzinfo=utc)
>>>> b = a.astimezone(norway)
>
> Your suggestion is really appreciated..

(posting reply on-list, hope that's okay!)

That would be fine for the normal case. It's just possible that the
user will change the computer's clock, which would result in the
serial changing oddly. If that's not a problem to you, the job's done!

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Issue with continous incrementing of unbroken sequence for a entire working day Chris Angelico <rosuav@gmail.com> - 2013-03-01 18:59 +1100

csiph-web