-
-
Notifications
You must be signed in to change notification settings - Fork 7
cell with =24/2 formatted as hour results in "ValueError: invalid literal for int() with base 10: 'H0'" #6
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
Comments
It was reproduced here with even LibreOffice Spreadsheet 4.1. Here is what it carries:
'PT288H00M00S' violates this spec: PThhHmmMss,ffffS hence kills the 'time_value' converter. Will find a workround for it. |
Have you checked whatever there is already LibreOffice bug report for that problem? It will probably lay unfixed for years but... |
Just googled a bit and seems google didn't know much about it. I found the simpler step to reproduce:
|
Facing various choices that I could do, I think it makes sense to throw a readable exception to the pyexcel_ods user/developer that he/she needs to fix the formatting in the ods file. I could not give a default value for such field, could I? |
Good job. I will code up a nice exception handler at the mean time. |
Somebody posted in https://bugs.documentfoundation.org/show_bug.cgi?id=97631 claim that this behaviour of LO is not violating spec. |
Had a look. day field could be '[0-9]+' instead of '[0-9]{2}'. For future reference, I am copying the iso link here: https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#duration Will make a fix. |
Thanks! |
released to pypi. thanks for your persistence. |
I am trying example from readme and on
To reproduce:
=24/2
into A1 cell23:00
into A2 cellOds file was created with LibreOffice Calc - Version: 5.0.4.2, Build ID: 1:5.0.4
rc2-0ubuntu1trusty1, Locale: pl-PL (en_US.UTF-8). Running on Ubuntu 14.04.Would it be useful to upload this .ods file somewhere or is it reproducible also in other environments?
The text was updated successfully, but these errors were encountered: