[Tutor] Wading through traceback output :p:

[Joel Goldstick]

On Mon, Dec 26, 2011 at 12:04 PM, Alan Gauld <alan.gauld at btinternet.com> wrote:
> On 26/12/11 12:52, Thomas C. Hicks wrote:
>
>> Also appreciate the thoughts about the file name.  This is my first big
>> project and I still have much to learn.  If you can point me to a
>> discussion of file naming when there are multiple files involved in a
>> project I am game to do some reading!
>
>
> When dealing with multiple files the only p[roblem tends to e if you have
> duplicate names. In that case create separate folders (packages in Python)
> and use namespaces to kep them separate.
>
> If you have multiple versions of the same file it's probably better to keep
> separate folders for each project version. But better still is to use a
> version control tool (which does the same thing virtually with a friendly
> UI/CLI and copes with multiple versions etc).
>
> These can range from simple file based RCS to full project based control.
> Most folks these days tenmd to go with project based
> control. CVS, SVN. GIT, Mercurial are the big names for freeware.
> [MS SourceSafe, IBM ClearCase and AidedeCamp are the big commercial players
> - but they cost big bucks(apart from SourceSafe)]
>
> SVN and Mercurial would be my suggestion, GUI front ends exist for both and
> both have packages for most Linux distros. They both have web sites with
> tutorials, but whiole there are oodles of options etc there are only a few
> commands you need for normal use, especially for a single user:
>
> create,
> check out,
> check in,
> fork,
> diff,
> merge
>
> should cover it.
>
>
> --
> 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

I sent this earlier but it doesn't look like it went through:

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