Duncan Murdoch
2020-Jun-06 19:53 UTC
[Rd] Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
On 06/06/2020 3:44 p.m., Duncan Murdoch wrote:> On 06/06/2020 3:06 p.m., Dirk Eddelbuettel wrote:... [deletions]>> In short, 4.0.0 no longer exports via 'exportPattern("^[[:alpha:]]+")' >> rendering the new package created non-functional. >> >> Was this intentional, or is this a bug we can look into fixing for R 4.0.2 ? > > It's in the NEWS, so I'd assume it was intentional: > > - package.skeleton() now explicitly lists all exports in the > ?NAMESPACE? file. > > An earlier version of that message even showed up in the link you posted.Something else in that link is presented more obviously in the svn log entry: r76945 | hornik | 2019-08-10 04:13:48 -0400 (Sat, 10 Aug 2019) | 1 line Changed paths: M /trunk/doc/NEWS.Rd M /trunk/src/library/utils/R/package.skeleton.R Have package.skeleton() explicitly list all exports. This change happened in August, 2019, about 10 months ago. Perhaps this message asking people to test R-devel is relevant: https://stat.ethz.ch/pipermail/r-devel/2020-May/079484.html Duncan Murdoch
Dirk Eddelbuettel
2020-Jun-06 20:14 UTC
[Rd] Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
On 6 June 2020 at 15:53, Duncan Murdoch wrote: | This change happened in August, 2019, about 10 months ago. Perhaps this | message asking people to test R-devel is relevant: | | https://stat.ethz.ch/pipermail/r-devel/2020-May/079484.html Touche :) And fully agree. Rcpp's unit tests covered Rcpp.package.skeleton() since about 2013. I have been keeping a local 'RD' build of R-devel in /usr/local/ for much longer to test both r-release and r-devel. But test coverage is never full or complete, and what bit me here during a live demo (now at [1]) was the equivalent functionality tickled with from RStudio with similar-but-not-identical code. And that part is certainly NOT contained in the unit tests. Can't win'em all. Still my bad for not checking NEWS, and bad luck this change did not get tickled by the many Rcpp tests runs here since the change was made. Dirk [1] https://www.youtube.com/watch?v=1Zap6j1uUyw -- http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
Duncan Murdoch
2020-Jun-06 22:05 UTC
[Rd] Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
On 06/06/2020 4:14 p.m., Dirk Eddelbuettel wrote:> > On 6 June 2020 at 15:53, Duncan Murdoch wrote: > | This change happened in August, 2019, about 10 months ago. Perhaps this > | message asking people to test R-devel is relevant: > | > | https://stat.ethz.ch/pipermail/r-devel/2020-May/079484.html > > Touche :) And fully agree. Rcpp's unit tests covered Rcpp.package.skeleton() > since about 2013. I have been keeping a local 'RD' build of R-devel in > /usr/local/ for much longer to test both r-release and r-devel. But test > coverage is never full or complete, and what bit me here during a live demo > (now at [1]) was the equivalent functionality tickled with from RStudio with > similar-but-not-identical code. > > And that part is certainly NOT contained in the unit tests. Can't win'em > all. Still my bad for not checking NEWS, and bad luck this change did not get > tickled by the many Rcpp tests runs here since the change was made.The trouble with tests is that they make you think you've tested the code, and we all know that's impossible. Duncan
Seemingly Similar Threads
- Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
- Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
- Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
- Possible Bug: file.exists() Function. Due to UTF-8 Encoding differences on Windows between R 4.0.1 and R 3.6.3?
- Rcpp 0.8.0 on CRAN