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

Groups > comp.lang.python > #77862

Re: CSV methodology

Show all headers | View raw

On 13Sep2014 21:34, jetrn@newsguy.com <jetrn@newsguy.com> wrote:
>Hello.  Back in the '80s, I wrote a fractal generator, [...]
>Anyway, something I thought would be interesting, would be to export
>some data from my fractal program (I call it MXP), and write something
>in Python and its various scientific data analysis and plotting modules,
>and... well, see what's in there.
>
>An example of the data:
>1.850358651774470E-0002
>32
>22
>27
>... (this format repeats)
>
>So, I wrote a procedure in MXP which converts "the data" and exports
>a csv file.  So far, here's what I've started with:

Normally a CSV file will have multiple values per row. Echoing Terry, what 
shape did you intend your CSV data to be? i.e. what values appear on a row?

>import csv
>fname = 'E:/Users/jayte/Documents/Python Scripts/XportTestBlock.csv'
>f = open(fname)
>reader = csv.reader(f)
>for flt in reader:
>    x = len(flt)
>file.close(f)
>
>This will get me an addressable array, as:
>
>flt[0], flt[1], flt[350], etc...  from which values can be assigned to
>other variables, converted...
>
>My question:  Is there a better way?  Do I need to learn more about
>how csv file are organized?  Perhaps I know far too little of Python
>to be attempting something like this, just yet.

If you have a nice regular CSV file, with say 3 values per row, you can go:

   reader = csv.reader(f)
   for row in reader:
       a, b, c - row

and proceed with a, b and c directly from there. But of course, that requires 
your export format to be usable that way.

Cheers,
Cameron Simpson <cs@zip.com.au>

For a good prime, call:  391581 * 2^216193 -1

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

Thread

CSV methodology jetrn@newsguy.com - 2014-09-13 21:34 -0400
  Re: CSV methodology kjs <bfb@riseup.net> - 2014-09-14 02:51 +0000
  Re: CSV methodology Terry Reedy <tjreedy@udel.edu> - 2014-09-14 03:02 -0400
    Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-14 12:56 -0400
      Re: CSV methodology Chris Angelico <rosuav@gmail.com> - 2014-09-15 03:10 +1000
      Re: CSV methodology Terry Reedy <tjreedy@udel.edu> - 2014-09-14 14:42 -0400
        Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-14 16:19 -0400
      Re: CSV methodology Peter Otten <__peter__@web.de> - 2014-09-15 09:29 +0200
        Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-15 12:33 -0400
          Re: CSV methodology Peter Otten <__peter__@web.de> - 2014-09-16 13:22 +0200
            Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-16 14:03 -0400
            Works perfectly (was Re: CSV methodology) jayte <jetrn@newsguy.com> - 2014-09-22 20:27 -0400
              Re: Works perfectly (was Re: CSV methodology) Peter Otten <__peter__@web.de> - 2014-09-23 09:59 +0200
  Re: CSV methodology Cameron Simpson <cs@zip.com.au> - 2014-09-14 18:38 +1000
    Re: CSV methodology Rustom Mody <rustompmody@gmail.com> - 2014-09-14 01:56 -0700
      Re: CSV methodology Cameron Simpson <cs@zip.com.au> - 2014-09-15 09:28 +1000
  Re: CSV methodology Akira Li <4kir4.1i@gmail.com> - 2014-09-15 11:12 +0400
    Re: CSV methodology pH <high@cidity.level> - 2014-09-15 12:40 -0400
  Re:CSV methodology Dave Angel <davea@davea.name> - 2014-09-15 09:29 -0400
    Re: CSV methodology jayte <jetrn@newsguy.com> - 2014-09-15 12:53 -0400

csiph-web