-
Notifications
You must be signed in to change notification settings - Fork 286
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
Why does readr::read_csv need timezone data and Olson database? #952
Comments
Because readr reads date times using it. Why doesn't your system have an Olson database? |
In our case, I think because it wasn't always part of the docker-stacks for jupyter? But that begs the question, is every machine We can fix it on our machines, but I opened this issue because I am not the only one who seems to have come across this problem. Wonder if it would be nice/possible for |
Yes, every machine readr is used on is expected to have a olsen database, the docker containers you are using are too stripped down. |
Thanks for the prompt response and explanation @jimhester! |
In docker container, here is a solution:
|
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/ |
This issue is closed, but I see no resolution: #320
I just ran into a similar situation today when teaching on a server. We were trying to use
readr::read_csv
to load this file: https://raw.githubusercontent.com/UBC-DSCI/dsci-100/master/materials/worksheet_01/marathon_small.csvOn one server which has tzdata installed, it works fine, on another that does not have this installed the following error message is given:
This csv file is very simple (see snippet below). Why does
readr::read_csv
need timezone data and Olson database? This GitHub issue, appears to tracking downreadr::read_csv
depending ontzdata
but why? Naively, it doesn't seem necessary, andread.csv
works fine on either server..csv
snippet:The smallest reproducible example I can get down to is this:
which on the problematic server gives:
So the problem likely stems from the
read_*
functions depending ondefault_locale()
for thelocale
argument by default. Is this really necessary? Naively, I think not, but I could be very wrong. Is there a way to saylocale = None/NA/etc
?This is not just a problem for me, as I have come across others experiencing the same problem...
The text was updated successfully, but these errors were encountered: