Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #51699
| References | <mailman.49.1375295978.1251.python-list@python.org> <ktbn0a$i7d$2@reader1.panix.com> |
|---|---|
| Date | 2013-07-31 14:35 -0500 |
| Subject | Re: Editing tabular data [was: PEP8 79 char max] |
| From | Skip Montanaro <skip@pobox.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.54.1375299334.1251.python-list@python.org> (permalink) |
>> My guess is it would be more foolproof to edit that stuff with a >> spreadsheet. > > Many years ago, I worked with somebody who used a spreadsheet like > that. I really love Emacs, however... One of the traders here where I work (who shall not be named) had a space-delimited data file with hundreds of rows and 50 or so columns. I could never get him to edit it in any kind of spreadsheet or put it in a database (expecting him to master SQL would have been pointless - I would have had to write a GUI tool for him). He always modified it in Emacs, and would delete columns, add extra spaces, fragmentary rows, etc. He'd edit this file late at night, the automated processes the next morning would crap out, and I would scramble to try and find and fix the problem before the market opened. This is clearly a case where choosing the proper tool is important. I agree that using a spreadsheet to edit a 3x5 CSV file is likely overkill (might just as well use Notepad or TextEdit), but tabular data are tabular data, no matter how they might be delimited, and if there are many of those little data critters, there are better tools than a text editor (or Python IDE) for maintaining them. Skip
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Editing tabular data [was: PEP8 79 char max] Skip Montanaro <skip@pobox.com> - 2013-07-31 13:39 -0500
Re: Editing tabular data [was: PEP8 79 char max] Grant Edwards <invalid@invalid.invalid> - 2013-07-31 19:02 +0000
Re: Editing tabular data [was: PEP8 79 char max] Skip Montanaro <skip@pobox.com> - 2013-07-31 14:35 -0500
Re: Editing tabular data [was: PEP8 79 char max] Chris Angelico <rosuav@gmail.com> - 2013-08-01 01:50 +0100
Re: Editing tabular data [was: PEP8 79 char max] Neil Cerutti <neilc@norwich.edu> - 2013-08-01 14:04 +0000
Re: Editing tabular data [was: PEP8 79 char max] wxjmfauth@gmail.com - 2013-08-02 02:15 -0700
Re: Editing tabular data Ben Finney <ben+python@benfinney.id.au> - 2013-08-02 16:35 +1000
Re: Editing tabular data rusi <rustompmody@gmail.com> - 2013-09-03 09:58 -0700
LibreOffice (was: Editing tabular data) Ben Finney <ben+python@benfinney.id.au> - 2013-08-02 17:14 +1000
Re: LibreOffice (was: Editing tabular data) Chris Angelico <rosuav@gmail.com> - 2013-08-02 10:37 +0100
Re: LibreOffice (was: Editing tabular data) Grant Edwards <invalid@invalid.invalid> - 2013-08-02 14:00 +0000
Re: LibreOffice Terry Reedy <tjreedy@udel.edu> - 2013-08-02 21:26 -0400
Re: LibreOffice David Robinow <drobinow@gmail.com> - 2013-08-03 11:08 -0400
Re: Editing tabular data [was: PEP8 79 char max] "Rhodri James" <rhodri@wildebst.demon.co.uk> - 2013-07-31 20:03 +0100
Re: Editing tabular data [was: PEP8 79 char max] Neil Cerutti <neilc@norwich.edu> - 2013-07-31 19:07 +0000
Re: Editing tabular data [was: PEP8 79 char max] Wanderer <wanderer@dialup4less.com> - 2013-07-31 13:37 -0700
Re: Editing tabular data [was: PEP8 79 char max] Skip Montanaro <skip.montanaro@gmail.com> - 2013-07-31 18:40 -0500
csiph-web