[Tutor] Wading through traceback output

[Joel Goldstick]

On Mon, Dec 26, 2011 at 7:10 AM, Alan Gauld <alan.gauld at btinternet.com> wrote:
> On 26/12/11 11:42, Thomas C. Hicks wrote:
>
> Given it was working before and not now the obvious question is what has
> changed? It looks like you are on a Linux box so do you have automatic
> updates switched on? Or do you always just accept the recommendation to
> update?
>
> In which case try looking at the modification dates of the
> library files....
>
> Also has the verion of Excel used to create the files changed?
>
> It looks like the point that the program leaves your code is here:
>
>
>>   File "./cttOverviewMain.0.03.2011.py", line 183, in writeMonthlyHeader
>>     sh.write(7,10,"# Locations",xlwt.easyxf('font: bold True'))
>
>
> So that points the finger at the xlwt module. If it has been updated has the
> format of that call changed - to a dictionary/tuple of values for example?
>
> These are all guesses but might give you a starting point.
>
>
> Incidentally cttOverviewMain.0.03.2011.py seems like a bizarre
> name for a file? I assume that's the date or somesuch? What is the thinking
> behind that?
>
> --
> Alan G
> Author of the Learn to Program web site
> http://www.alan-g.me.uk/
>
>
> _______________________________________________
> Tutor maillist  -  Tutor at python.org
> To unsubscribe or change subscription options:
> http://mail.python.org/mailman/listinfo/tutor

It may be that there is something different about your data with this
recent run.  I googled your error message and came up with this link:

http://groups.google.com/group/python-excel/browse_thread/thread/c717ad00c7acc848

I'm not familiar with the package, but ValueError: More than 4094 XFs
(styles) has lots of links on google.  To test my guess, would it be
possible for you to set up your application to run it on files that it
successfully worked on before?  If it won't work on them, then I'd
guess that a module may have updated.  But if it does work, then you
may have some condition in your new data that exercises your program
in a way it hasn't be exercised before that raises the exception.

The link I showed contains this little snippet:
-------------------------
On 27/09/2010 00:46, Keyton Weissinger wrote:

>                  if current_value_is_date:
>                      s = XFStyle()
>                      s.num_format_str = 'M/D/YY'
>                      export_sheet.write(row_idx, col_idx,
> current_value, s)

...and we have a winner.

Create the style *once* in your outermost part of the function and
re-used it, rather than creating a new style each and every time you
write a date cell...
-------------------------

I don't know if this situation applies to you, but maybe it will give you a clue

-- 
Joel Goldstick