Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[9.0] Installing python-xlrd package breaks CSV preview (and therefore import) #10199

Closed
bistaray opened this issue Dec 23, 2015 · 5 comments
Closed

Comments

@bistaray
Copy link

On Ubuntu 14.04 LTS, I have noticed that installing python-xlrd (0.9.2-1) breaks CSV preview (and therefore import).

By running sudo apt-get remove python-xlrd and restarting the server, CSV preview (and import) works again.

Note: Runbot instances do not appear to have python-xlrd library installed.


CSV preview (before import) without XLRD installed:
Without XLRD


CSV preview (before import) with XLRD installed:
With XLRD


On runbot, I always get the first (success), but when I try to import an XLSX file, I get:

Import preview failed due to: Unable to load "xlsx" file: requires Python module "xlrd >= 0.8".

@bistaray bistaray changed the title [9.0] Installing xlrd package breaks CSV preview (and therefore import) [9.0] Installing python-xlrd package breaks CSV preview (and therefore import) Dec 23, 2015
@boscoerp
Copy link

Facing same issue.

image

any work around !

@bistaray
Copy link
Author

I can't replicate this on runbot as of today (http://139699-9-0-f4cc88.runbot.odoo.com/). I am now wondering if this has been resolved. Runbot now seems to have py-xlrd installed (because XLS import works).

@bistaray
Copy link
Author

bistaray commented Apr 9, 2016

However, the SAAS version is UNABLE to import XLS files:

Import preview failed due to: Unable to load "xls" file: requires Python module "xlrd".

For CSV files, the issue could be an incorrect encoding.

@wtaferner
Copy link
Contributor

@bistaray
Not sure about the SaaS but at least a big part of the issue was fixed in #10374 in two steps.

@Yenthe666
Copy link
Collaborator

I believe this was all handled & fixed (as @wtaferner pointed out).
Don't hesitate to comment / reopen if you can still reproduce it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants