rpython - R package to embed Python which supports reference sharing both ways - check results
RForge.net

rpython

About rpython
GIT access
Download/Files
Check results

Result: WARNING
Check time: 2017-07-19 18:29
* using log directory '/www/rforge/projects/rpython/check/rpython2.Rcheck'
* using R version 3.3.3 Patched (2017-03-15 r72928)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: ISO8859-1
* checking for file 'rpython2/DESCRIPTION' ... OK
* this is package 'rpython2' version '0.1-0'
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for executable files ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package 'rpython2' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking DESCRIPTION meta-information ... NOTE
Malformed Description field: should contain one or more complete sentences.
License components which are templates and need '+ file LICENSE':
MIT
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... OK
* checking Rd files ... WARNING
prepare_Rd: py.attr.Rd:26-27: Dropping empty section \value
prepare_Rd: py.get.Rd:7-9: Dropping empty section \description
prepare_Rd: py.get.Rd:26-32: Dropping empty section \value
checkRd: (5) py.get.Rd:0-46: Must have a \description
* checking Rd metadata ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... WARNING
Undocumented code objects:
'as.pyref' 'py.eval' 'py.exception' 'py.last.exception' 'py.load'
'py.rcaps'
All user-level objects in a package should have documentation entries.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... NOTE
S3 methods shown with full name in documentation object 'py.attr':
'$.pyref' '$<-.pyref'

The \usage entries for S3 methods should use the \method markup and not
their full name.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking compilation flags in Makevars ... OK
* checking for GNU extensions in Makefiles ... WARNING
Found the following file(s) containing GNU extensions:
src/Makevars
Portable Makefiles do not use GNU extensions such as +=, :=, $(shell),
$(wildcard), ifeq ... endif. See section 'Writing portable packages' in
the 'Writing R Extensions' manual.
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking compiled code ... OK
* checking examples ... OK
* checking PDF version of manual ... OK
* DONE

Status: 3 WARNINGs, 2 NOTEs
See
'/www/rforge/projects/rpython/check/rpython2.Rcheck/00check.log'
for details.


Distribution log

SVN checkout/GIT clone log