xlrd 0.7.2 released!

[Chris Withers]

Hi All,

I'm pleased to announce the release of xlrd 0.7.2. This release, like
the xlwt release, is long overdue and has been over 2.5 years in the making!

The highlights:

- All messaging and debug logging is now written to the logfile provided
to open_workbook.

- Tolerant handling of file with non-standard compound document header

- Tolerant handling of files with extra zero bytes at end of NUMBER record

- Handle mostly-BIFF8 file with BIFF5-7 WINDOWS2 record

- Handle dodgy version 2.x .xls files.

- Added support for HYPERLINK extraction

- Added access to cell notes/comments.

- Enable reading files created by pyXLWriter -- puts BIFF8 MERGEDCELLS
record in a BIFF5 file.

- Fixed a file-locking issue on Windows when an exception was raised in
open_workbook() and on_demand was True

- Book objects are now context managers

- Rich text formatting information is now extracted

- Page breaks information is now extracted

- Some improvements in zoom factor handling

- PANE records are now processed

- Some memory and performance enhancements

For a full list of the changes, please see the svn log:

https://secure.simplistix.co.uk/svn/xlrd/trunk

I've currently only put up .tar.gz sdists, if anyone requires anything
else, please explain why and I'll be happy to add!

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
--
http://mail.python.org/mailman/listinfo/python-list

[python-excel]

Chris Withers wrote:

> Hi All,
>
> I'm pleased to announce the release of xlrd 0.7.2. This release,
> like the xlwt release, is long overdue and has been over 2.5 years
> in the making!
> [...snip...]
>
> I've currently only put up .tar.gz sdists, if anyone requires
> anything else, please explain why and I'll be happy to add!

hi,

a windows installer exe would be good for the same reasons it
was good for previous versions. two reasons that spring to mind
immediately are:

 - it makes it much easier to tell what version is installed
 - it makes it much easier to uninstall the package

i know that both of these are things that the python community
does not yet seem to find useful but everyone else seems to.

for instance, if i just install the new versions of these packages
on windows, it will replace the python-specific files that were
associated with the previous version but it will have no impact
on the system's list of installed software so if i look at the
add/remove software control panel, it will happily tell me that
i still have the previous versions. on the other hand, if the new
versions were installed with windows installers, they would be able
to properly replace the old versions with the new versions and make
it clear that it has done do.

knowing this, i will of course uninstall the old versions before
installing the new versions so at least windows won't be forced
to lie to me about what versions are installed.

of course, i might be wrong about all of this and setup.py may manage
the windows installed software list properly and do a proper upgrade.
if so, sorry for wasting time.

cheers,
raf

--
http://mail.python.org/mailman/listinfo/python-list

[Chris Withers]

On 22/02/2012 00:37, [hidden email] wrote:
> was good for previous versions. two reasons that spring to mind
> immediately are:
>
>   - it makes it much easier to tell what version is installed
>   - it makes it much easier to uninstall the package
>
> i know that both of these are things that the python community
> does not yet seem to find useful but everyone else seems to.

That's because it's no longer best practice to polute the global python
installation by installing packages directly into it.

The recommended wisdom nowadays is to use a virtualenv and then pip
install the package.

I believe that will give you everything you need, please explain if it
doesn't.

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
--
http://mail.python.org/mailman/listinfo/python-list

[python-excel]

Chris Withers wrote:

> On 22/02/2012 00:37, [hidden email] wrote:
> >was good for previous versions. two reasons that spring to mind
> >immediately are:
> >
> >  - it makes it much easier to tell what version is installed
> >  - it makes it much easier to uninstall the package
> >
> >i know that both of these are things that the python community
> >does not yet seem to find useful but everyone else seems to.
>
> That's because it's no longer best practice to polute the global
> python installation by installing packages directly into it.
>
> The recommended wisdom nowadays is to use a virtualenv and then pip
> install the package.
>
> I believe that will give you everything you need, please explain if
> it doesn't.
>
> cheers,
>
> Chris

thanks. i'm sure that'll do nicely.

cheers,
raf

--
http://mail.python.org/mailman/listinfo/python-list

[Adrian Klaver-2]

On Wednesday, February 22, 2012 5:22:45 am Chris Withers wrote:

> On 22/02/2012 00:37, [hidden email] wrote:
> > was good for previous versions. two reasons that spring to mind
> >
> > immediately are:
> >   - it makes it much easier to tell what version is installed
> >   - it makes it much easier to uninstall the package
> >
> > i know that both of these are things that the python community
> > does not yet seem to find useful but everyone else seems to.
>
> That's because it's no longer best practice to polute the global python
> installation by installing packages directly into it.
>
> The recommended wisdom nowadays is to use a virtualenv and then pip
> install the package.

I can see where that would be preferred when managing multiple versions of
Python, but not when using a single version.  The pip system does a good job of
managing package installs in the global context. As to the OPs original post, I
see the point. On Windows the installer is the point of entry for 'package'
management, going outside that can get confusing. I also understand setting up a
Windows installer is non-trivial. Assuming a Windows installer is not in the
offing, the OP might find it easier to use the Python packaging from here on out.  
For an example, to find out information on a package:

aklaver@tucker:~/.pip$ pip  search xlrd
xlutils                   - Utilities for working with Excel files that require
both xlrd and xlwt
xlrd                      - Library for developers to extract data from
Microsoft Excel (tm) spreadsheet files
  INSTALLED: 0.7.2 (latest)
xlrd3                     - Library for developers to extract data from
Microsoft Excel (tm) spreadsheet files
xlrd1                     - library for extracting data from Microsoft Excel
spreadsheet files


>
> I believe that will give you everything you need, please explain if it
> doesn't.
>
> cheers,
>
> Chris

--
Adrian Klaver
[hidden email]
--
http://mail.python.org/mailman/listinfo/python-list

[Chris Withers]

On 22/02/2012 23:17, Adrian Klaver wrote:
> I can see where that would be preferred when managing multiple versions of
> Python, but not when using a single version.

Sorry, I don't agree. It is *never* a good idea to install packages
globally. Using virtualenv or similar (buildout, etc) gives you a
single, cross platform way of not ending up with a mess of a python
installation where you have a bunch of libraries of random versions
installed, often with no way of finding out what version they are or how
to uninstall them.

Heaven forbid you want to use or develop more than one project per
machine; then you end up with different projects needing different
versions of the same libraries and you're screwed. ;-)

> The pip system does a good job o
> managing package installs in the global context.

Ask the pip maintainers whether they'd suggest using pip on the global
system python or inside a virtualenv...

> see the point. On Windows the installer is the point of entry for 'package'
> management, going outside that can get confusing.

"Python" should be though of as the application, not any individual
library...

> I also understand setting up a
> Windows installer is non-trivial.

It isn't a lot of work from what I remember, I just don't like
encouraging bad practices...

> offing, the OP might find it easier to use the Python packaging from here on out.

What is "the Python packaging" you refer to?

> xlrd3                     - Library for developers to extract data from
> Microsoft Excel (tm) spreadsheet files
> xlrd1                     - library for extracting data from Microsoft Excel
> spreadsheet files

I would avoid both of these like the plague, it's a shame the people who
dumped them on PyPI don't put up a similar warning :-(

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
--
http://mail.python.org/mailman/listinfo/python-list

[xlstime]

Hi,

i want to learn pyxl  please help me...

kindly send useful information about pyxl


Thank you in Advance
XLS S :)

On Thu, Feb 23, 2012 at 4:45 AM, <[hidden email]> wrote:

Chris Withers wrote:

> On 22/02/2012 00:37, [hidden email] wrote:
> >was good for previous versions. two reasons that spring to mind
> >immediately are:
> >
> >  - it makes it much easier to tell what version is installed
> >  - it makes it much easier to uninstall the package
> >
> >i know that both of these are things that the python community
> >does not yet seem to find useful but everyone else seems to.
>
> That's because it's no longer best practice to polute the global
> python installation by installing packages directly into it.
>
> The recommended wisdom nowadays is to use a virtualenv and then pip
> install the package.
>
> I believe that will give you everything you need, please explain if
> it doesn't.
>
> cheers,
>
> Chris

thanks. i'm sure that'll do nicely.

cheers,
raf

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

--
.........................


--
http://mail.python.org/mailman/listinfo/python-list

[Chris Withers]

On 23/02/2012 14:40, xlstime wrote:
> Hi,
>
> i want to learn pyxl  please help me...
>
> kindly send useful information about pyxl

I would suggest:

- using your real name when posting
- reading the tutorial at http://www.python-excel.org/

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
--
http://mail.python.org/mailman/listinfo/python-list