Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #103147 > unrolled thread
| Started by | Tim Chase <python.list@tim.thechases.com> |
|---|---|
| First post | 2016-02-18 13:20 -0600 |
| Last post | 2016-02-18 13:20 -0600 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Question on keyword arguments Tim Chase <python.list@tim.thechases.com> - 2016-02-18 13:20 -0600
| From | Tim Chase <python.list@tim.thechases.com> |
|---|---|
| Date | 2016-02-18 13:20 -0600 |
| Subject | Re: Question on keyword arguments |
| Message-ID | <mailman.21.1455824012.2289.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web