Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #77283
| Date | 2014-08-29 12:02 -0700 |
|---|---|
| From | Ethan Furman <ethan@stoneleaf.us> |
| Subject | suckitude classifications [was Re: Keeping python code and database in sync] |
| References | <mailman.13604.1409316126.18130.python-list@python.org> <roy-AE646E.10535529082014@news.panix.com> <CANc-5UxEY4XgmoiNa5MR=1Hy8SeRtpr1r=rRjBFKw2RrxFNomQ@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.13616.1409338966.18130.python-list@python.org> (permalink) |
On 08/29/2014 10:04 AM, Skip Montanaro wrote: > On Fri, Aug 29, 2014 at 9:54 AM, Roy Smith <roy@panix.com> wrote: >> Yeah, schema migration is an ugly problem. > > It's not really any worse than any other sort of complex data > structure change, is it? If your persistent data lived in a pickle > file, it would likely be as bad or worse. > >> ... suckitude ... > > Nice word. Let's use it more so my polly app will see it as a common > word and maybe offer it to me in a potential XKCD 936 password. :-) > > suckitude suckitude suckitude suckitude suckitude suckitude suckitude Speaking of suckitude, we could classify technologies that way: xml: major suckitude rpc: no suckitude python: negative suckitude oh, and suckitude is neither cruft nor corpus ! Polly want a cracker? ;) -- ~Ethan~
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Keeping python code and database in sync "Frank Millman" <frank@chagford.com> - 2014-08-29 14:42 +0200
Re: Keeping python code and database in sync Rustom Mody <rustompmody@gmail.com> - 2014-08-29 05:55 -0700
Re: Keeping python code and database in sync "Frank Millman" <frank@chagford.com> - 2014-08-29 15:19 +0200
Re: Keeping python code and database in sync Roy Smith <roy@panix.com> - 2014-08-29 10:54 -0400
Re: Keeping python code and database in sync Skip Montanaro <skip@pobox.com> - 2014-08-29 12:04 -0500
suckitude classifications [was Re: Keeping python code and database in sync] Ethan Furman <ethan@stoneleaf.us> - 2014-08-29 12:02 -0700
Re: Keeping python code and database in sync Ben Finney <ben+python@benfinney.id.au> - 2014-08-30 06:34 +1000
Re: Keeping python code and database in sync Chris Angelico <rosuav@gmail.com> - 2014-08-30 08:31 +1000
Re: suckitude classifications [was Re: Keeping python code and database in sync] Chris Angelico <rosuav@gmail.com> - 2014-08-30 08:38 +1000
Re: suckitude classifications [was Re: Keeping python code and database in sync] Roy Smith <roy@panix.com> - 2014-08-29 19:19 -0400
Re: suckitude classifications [was Re: Keeping python code and database in sync] Chris Angelico <rosuav@gmail.com> - 2014-08-30 09:38 +1000
Re: Keeping python code and database in sync Skip Montanaro <skip.montanaro@gmail.com> - 2014-08-29 18:47 -0500
Re: Keeping python code and database in sync Ethan Furman <ethan@stoneleaf.us> - 2014-08-29 16:54 -0700
Re: Keeping python code and database in sync Skip Montanaro <skip@pobox.com> - 2014-08-29 21:14 -0500
Re: Keeping python code and database in sync Chris Angelico <rosuav@gmail.com> - 2014-08-30 12:28 +1000
Re: suckitude classifications {taken to absurdity} Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-08-30 11:13 -0400
csiph-web