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


Groups > comp.lang.python > #103147

Re: Question on keyword arguments

From Tim Chase <python.list@tim.thechases.com>
Newsgroups comp.lang.python
Subject Re: Question on keyword arguments
Date 2016-02-18 13:20 -0600
Message-ID <mailman.21.1455824012.2289.python-list@python.org> (permalink)
References <62136715E19142B6B318EA3A3DF04D40@OPTIPLEX990> <na4kut$ru8$1@ger.gmane.org> <7278ec3f250548b192ce2d95c6fa07c5@seaexchmbx03.olympus.F5Net.com> <CAPTjJmoSX8stV5FBLALGctahP++n6+xfbMy6nXa0PMTr0aS17w@mail.gmail.com> <52FA2B3109D743E2BB8534CAC2B5E8A5@OPTIPLEX990>

Show all headers | View raw


On 2016-02-18 10:57, grsmith@atlanticbb.net wrote:
> Tim, the 'crazy-other-result format' is the
> result returned by the database, nothing
> I can do about that :)

then, much like converting byte-strings to unicode strings as early
as possible and converting them back to byte-strings as late as
possible, I'd do the same with your DB results:  change them into
real Python lists as soon as they come out of the DB, operate on them
throughout your code as real lists, and only convert them back to
crazy-other-format at the time you write them back to the DB.

My condolences on having to deal with ugly data.  Been there, done
that, still stuck with it. :-)

-tkc

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


Thread

Re: Question on keyword arguments Tim Chase <python.list@tim.thechases.com> - 2016-02-18 13:20 -0600

csiph-web