-
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
Implicit vs explicit printing of problems #726
Comments
I'm getting (i think) the same printing problem parsing failure warning even with
|
The printing issues look to be fixed in the devel version library(readr)
url <- "https://raw.githubusercontent.com/STAT545-UBC/STAT545-UBC.github.io/master/gapminderDataFiveYear_dirty.txt"
df <- read_table2(url)
#> Parsed with column specification:
#> cols(
#> year = col_double(),
#> pop = col_double(),
#> lifeExp = col_double(),
#> gdpPercap = col_double(),
#> region = col_character()
#> )
#> Warning: 326 parsing failures.
#> row col expected actual file
#> 145 -- 5 columns 7 columns 'https://raw.githubusercontent.com/STAT545-UBC/STAT545-UBC.github.io/master/gapminderDataFiveYear_dirty.txt'
#> 146 -- 5 columns 7 columns 'https://raw.githubusercontent.com/STAT545-UBC/STAT545-UBC.github.io/master/gapminderDataFiveYear_dirty.txt'
#> 147 -- 5 columns 7 columns 'https://raw.githubusercontent.com/STAT545-UBC/STAT545-UBC.github.io/master/gapminderDataFiveYear_dirty.txt'
#> 148 -- 5 columns 7 columns 'https://raw.githubusercontent.com/STAT545-UBC/STAT545-UBC.github.io/master/gapminderDataFiveYear_dirty.txt'
#> 149 -- 5 columns 7 columns 'https://raw.githubusercontent.com/STAT545-UBC/STAT545-UBC.github.io/master/gapminderDataFiveYear_dirty.txt'
#> ... ... ......... ......... ............................................................................................................
#> See problems(...) for more details. Created on 2017-12-07 by the reprex package (v0.1.1.9000). |
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/ |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're reading an (intentionally) tricky file in via readr. We hadn't planned on anyone using
read_table()
orread_table2()
and yet ... someone did. Their expectation that these functions would work supports the viewpoint in #717 (makeread_table()
behave likeread.table()
).Anyway, there are many problems, which makes sense. But the printing of the problems during import vs. explicit print after the fact suggests there's a printing problem.
The text was updated successfully, but these errors were encountered: