Re: xlrd and cPickle.dump

2008-04-02 Thread John Machin
[EMAIL PROTECTED] wrote: >> FWIW, it works here on 2.5.1 without errors or warnings. Ouput is: >> 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit (Intel)] >> 0.6.1 > > I guess it's a version issue then... I say again: Don't guess. > > I forgot about sorted! Yes, that would make sen

Re: xlrd and cPickle.dump

2008-04-02 Thread patrick . waldo
>FWIW, it works here on 2.5.1 without errors or warnings. Ouput is: >2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit (Intel)] >0.6.1 I guess it's a version issue then... I forgot about sorted! Yes, that would make sense! Thanks for the input. On Apr 2, 4:23 pm, [EMAIL PROTECTED]

Re: xlrd and cPickle.dump

2008-04-02 Thread Konstantin Veretennicov
On Wed, Apr 2, 2008 at 5:23 PM, <[EMAIL PROTECTED]> wrote: > Still no luck: > > Traceback (most recent call last): > File "C:\Python24\Lib\site-packages\pythonwin\pywin\framework > \scriptutils.py", line 310, in RunScript >exec codeObject in __main__.__dict__ > File "C:\text analysis\pickle_

Re: xlrd and cPickle.dump

2008-04-02 Thread patrick . waldo
Still no luck: Traceback (most recent call last): File "C:\Python24\Lib\site-packages\pythonwin\pywin\framework \scriptutils.py", line 310, in RunScript exec codeObject in __main__.__dict__ File "C:\text analysis\pickle_test2.py", line 13, in ? cPickle.dump(Data_sheet, pickle_file, -1)

Re: xlrd and cPickle.dump

2008-04-01 Thread John Machin
On Apr 2, 7:19 am, [EMAIL PROTECTED] wrote: > > How many megabytes is "extremely large"? How many seconds does it take > > to open it with xlrd.open_workbook? > > The document is 15mb ad 50,000+ rows (for test purposes I will use a > smaller sample), 15 Mb is not large. E.g. 120 Mb is large. > bu

Re: xlrd and cPickle.dump

2008-04-01 Thread patrick . waldo
> How many megabytes is "extremely large"? How many seconds does it take > to open it with xlrd.open_workbook? The document is 15mb ad 50,000+ rows (for test purposes I will use a smaller sample), but my computer hangs (ie it takes a long time) when I try to do simple manipulations and the documen

Re: xlrd and cPickle.dump

2008-04-01 Thread John Machin
[EMAIL PROTECTED] wrote: > Hi all, > > Sorry for the repeat I needed to reform my question and had some > problems...silly me. Indeed. Is omitting the traceback part of the "reformation"? > > The xlrd documentation says: > "Pickleable. Default is true. In Python 2.4 or earlier, setting to > fa

xlrd and cPickle.dump

2008-04-01 Thread patrick . waldo
Hi all, Sorry for the repeat I needed to reform my question and had some problems...silly me. The xlrd documentation says: "Pickleable. Default is true. In Python 2.4 or earlier, setting to false will cause use of array.array objects which save some memory but can't be pickled. In Python 2.5, ar

xlrd and cPickle.dump

2008-03-31 Thread patrick . waldo
Hi all, I have to work with a very large excel file and I have two questions. First, the documentation says that cPickle.dump would be the best way to work with it. However, I keep getting: Traceback (most recent call last): File "C:\Python24\Lib\site-packages\pythonwin\pywin\framework \script

xlrd and cPickle.dump/rows to list

2008-03-31 Thread patrick . waldo
Hi all, I have to work with a very large excel file and I have two questions. First, the documentation says that cPickle.dump would be the best way to work with it. However, I keep getting: Traceback (most recent call last): File "C:\Python24\Lib\site-packages\pythonwin\pywin\framework \script