> > I can't find one reference to Python in the documentation:
> Maybe because it's *not* needed? There's a note here though:
Thank you.
I'm deleting it.
[[alternative HTML version deleted]]
__
R-devel@r-project.org mailing list
https://stat.et
On Sat, 3 Aug 2019 at 00:36, Abby Spurdle wrote:
>
> I can't find one reference to Python in the documentation:
Maybe because it's *not* needed? There's a note here though:
https://github.com/rwinlib/gcc-4.9.3
Iñaki
__
R-devel@r-project.org mailing li
(Excerpts only).
On Sat, Aug 3, 2019 at 12:48 AM Jeroen Ooms wrote:
> > I'm assuming that Python is required to build R packages, on all
operating
> > systems.
> Please don't assume but read the documentation (preferably before
posting).
I can't find one reference to Python in the documentation:
If you can run things on LInux try running a few iterations of that loop
under valgrind, setting gctorture(TRUE) before the loop.
% R --debugger=valgrind --silent
> gctorture(TRUE)
> for(i in 1:5) { ... body of your loop ... }
valgrind can show memory misuse that eventually will cause R to crash.
On 2 August 2019 at 16:23, Sun Yijiang wrote:
| The R script I run daily for hours looks like this:
|
| while (!finish) {
| Sys.sleep(0.1)
| time = as.integer(format(Sys.time(), "%H%M")) # always crash here
| if (new.data.timestamp() <= time)
| next
| # ... do some jobs f
On Fri, Aug 2, 2019 at 12:12 AM Abby Spurdle wrote:
>
> I've just discovered that Rtools (on Windows) contains Python
> interpreter(s).
A minimal build of python was included as a dependency of gdb in
Rtools 3.3 and up.
> I'm assuming that Python is required to build R packages, on all operating
> It is pure native R annotation, I mean à la java. I wish to have an @
> operator available a R language level to create/embed real code
> annotations. Currently, the best I can get is to use a trick of hiding such
> thing behind a comment. Neither good, not the right way, as comments are
> commen
In an optimized build, debug info is just an approximation. It might
help to debug in a build of R and packages without compiler
optimizations (-O0), where the debug information is accurate. However,
first I would try to modify the example to trigger more often, or try to
find external ways to
The R script I run daily for hours looks like this:
while (!finish) {
Sys.sleep(0.1)
time = as.integer(format(Sys.time(), "%H%M")) # always crash here
if (new.data.timestamp() <= time)
next
# ... do some jobs for about 2 minutes ...
gc()
}
Basically it waits for new da
write.dcf(list('my-field' = 1L), tmp <- tempfile())
cat(readLines(tmp))
# my.field: 1
However there's nothing wrong with hyphenated fields per the Debian
standard:
https://www.debian.org/doc/debian-policy/ch-controlfields.html
And in fact we see them using hyphenated fields there, and indeed re
Good evening R devel mailing list.
Just wonder if there is a way to ask for an evolution of the R language. In
affirmative case, let me know.
I use R for now many years, and still like it very much. It evolves quite
smoothly and improves well. Nevertheless, there is one topic that I still
miss in
Is the win-builder site (https://win-builder.r.project.org) down? I cannot load
the tarball for my package to the development branch. I can upload it on the
release and old-release branches.
Also get FTP error (Failed FTP upload: 550) when I run
devtools::check_win_devel().
Package is at htt
12 matches
Mail list logo
