Re: [R] strptime() keeps emitting warnings after establishing a handler with tryCatch()

Thanks, Rui, for checking on your end. I don't think any Linux-based system is affected, as they silently ignore invalid timezone identifiers (at least the versions I know of). I now also had a chance to test on Windows 10 and get the same errors as under macOS. The session info for this test is

[R] analyzing results from Tuesday's US elections

Hello: What can you tell me about plans to analyze data from this year's general election, especially to detect possible fraud? I might be able to help with such an effort. I have NOT done much with election data, but I have developed tools for data analysis, including web scr

Re: [R] strptime() keeps emitting warnings after establishing a handler with tryCatch()

Hello, I cannot reproduce this behavior and, as documented, the posted code doesn't issue warnings due to a wrong timezone but I'm running sessionInfo() R version 4.0.3 (2020-10-10) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Ubuntu 20.04.1 LTS Matrix products: default BLAS: /usr

[R] strptime() keeps emitting warnings after establishing a handler with tryCatch()

Dear list members, I have come about a peculiar behavior in R (4.0.2) which I would describe as a bug. On macOS, where `strptime()` raises a warning for invalid timezone identifiers, the following code will continue to raise the original warning with every subsequent call to `strptime()`: ``` # a