xlrd and xlwt releases

[Chris Withers]

Hi All,

It's been far too long since there have been any xlwt and xlwrd
releases, I have the power so I'm thinking of cutting some ;-)

Unless anyone objects, I'll be cutting releases based from current trunk
as soon as possible.

I'd then like to do two further releases:

- an xlrd release with xlsxrd merged in

- an xlwt release containing autofit.

I'd be interested in people's thoughts...

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

[RHouse]

Hi Chris,
Good proposal. +1 on the xlsx stuff from me. That would save me re-saving users spreadsheets as xls.
In the past  I have missed having autofit, so +1 on that as well.

Regards,
Richard

[David Hoffman]

Yes, excellent, Chris.  Thanks!

[John Machin]

Hi Chris,

Thanks for the offer (and all the nagging!).

xlwt trunk is ready to be released as version 0.7.3. (N.B. three very recent commits). Go for it!

xlrd will be ready as 0.7.2 in a day or two (some documentation changes and some minor tidying).
Note that as previously discussed I want to announce that 0.7.2 will be the last version to support Python 2.1 and 2.2.

I'd be very happy for you to put "autofit" into xlwt.

I'd very much prefer to do the xlsxrd stuff myself, if I have the time. Let's review the schedule weekly.

Cheers,
John

[Harald Armin Massa[legacy]]

Unless anyone objects, I'll be cutting releases based from current trunk as soon as possible.

I'd then like to do two further releases:

- an xlrd release with xlsxrd merged in

- an xlwt release containing autofit.

I'd be interested in people's thoughts...

I like this plans. 

Harald

 

--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
Using PostgreSQL is mostly about sleeping well at night.

[alain legault]

Hi Chris

a +1E99 for getting xlsxrd merged in...somebody just threw an xlsx my
way :-0 VERY timely.

many thanks

Alain

[Matt Smith]

I would love to have the xlsx reader. It would greatly lower my user
barriers to entry.

[Ash Krishan]

+1 Chris...excellent thought.

> --
> You received this message because you are subscribed to the Google Groups "python-excel" group.
> To post to this group, send an email to python...@googlegroups.com.
> To unsubscribe from this group, send email to python-excel...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/python-excel?hl=en-GB.
>

[Scott Michel]

Has the documentation been upgraded to use something resembling
docutils or sphinx?

[John Machin]

No. Why do you ask?

[Chris Withers]

On 20/02/2012 05:42, Scott Michel wrote:
> Has the documentation been upgraded to use something resembling
> docutils or sphinx?

Not the packages, no.

I'm contemplating sprinting on turning the tutorial into a Sphinx-based
project on GitHub.

If that goes okay, I'd maybe look to do xlutils, xlwt and then xlrd, in
that order.

Of course, I'm proving to be just as time constrained as John when it
comes to doing releases right now, so let's not hold our breath ;-)

[Scott Michel]

Usability. Whilst I do like to read other people's code to figure out
all of the hidden, cool features and I know how to open extra tabs
just to keep the various pages I need to keep handy, Sphinx-based
documentation just seems to be more comfortable.

Sorry if it came off a bit cheeky, but python.org's documentation is
nice and usable.

And to Chris: No need. I'm already there. Mostly. In progress and
relatively far along. And I kept the English spellings.

[Chris Withers]

On 21/02/2012 06:12, Scott Michel wrote:
> And to Chris: No need. I'm already there. Mostly. In progress and
> relatively far along. And I kept the English spellings.

Care to share?

[John Machin]

What hidden cool features have you found in xlrd? In what respect is xlrd's documentation not nice or not usable?

[Scott Michel]

@John: Can't say that I've found any hidden features, per se, but I
now understand xlrd's code better. xlrd's documentation could be less
sparse in places. Hyperlinking classes as they occur on the
documentation is also known to be a nice feature. With the current
documentation scheme, I end up having a lot of browser tab clutter
from having the various class documentation open.

Something that occurred to me whilst looking at XF: wouldn't it be
preferred to implement properties instead of the magic underscored
booleans?

One thing about using Sphinx for the documentation: it eliminates the
class variable documentation hack. Performance-wise, this is probably
not even noticeable. But it is hygenic.

@Chris: Of course I'm happy to share. Are you looking for something
interim or complete? I suspect complete is preferred.


-scooter

[Chris Withers]

On 23/02/2012 17:13, Scott Michel wrote:
> @Chris: Of course I'm happy to share. Are you looking for something
> interim or complete? I suspect complete is preferred.

It would be interesting to see the interim, where can I take a look?

[Scott Michel]

Haven't amended the patchset in a bit, but it's visible on github:
https://github.com/bscottm/xlrd

[Scott Michel]

To increase cluon flux density, look in the doc subdirectory. I'll try
to amend-commit the lastest set of edits later this evening (Pacific
time).

> >              -http://www.simplistix.co.uk- Hide quoted text -
>
> - Show quoted text -