the writer needs to set localSheetId to the sheet index, not the sheet name to correctly set the scope of a named range. This should correct the issue of the scope always defaulting to workbook instead of the proper worksheet when creating print titles.
Not quite. The unit test should test independently of the underlying method that a NamedRange with the right values has been created so you should either create a NamedRange using the relevant module, or, and this is preferable simply check the attributes of the object created.
Please let me know if there is anything in the docs that is unclear. I like to think of testing as little bit like jumping into cold water: nervous trepidation and some thrashing and then suddenly things don't seem so bad.
Pretty much. On a unix system you can just do tox and it will run the tests for all the configured environments. Takes a while the first time it runs because lxml has to get installed. But it picks up a lot of bugs on different system before we try and release anything.
Feel free to ask any questions on the mailing list.
py.test on the worksheet and workbook modules currently gives no errors, but I'm getting permission errors for writing to the temp folder during the xml portion of the test. Not sure why. Getting tox working properly is another story. I've posted to the group about the issues.
ah, looks like you didn't get my last commit. I updated worksheet.add_print_titles because using ._current_sheet_index always returns index 0 unless it's explicitly updated. Then I corrected the above error to expect the scope to be the index of the sheet rather than the name.
@Josh Haywood Are you making progress? I'd like to include this in a 2.2 release.
If you merge in the upstream changes then the weird failures in xmlfile should go away. This is down to the behaviour of NamedTemporaryFile on Windows and is a known bug for which there is no still no resolution apart from manually removing any temporary files. See http://bugs.python.org/issue14243 for the details.