similar to: Reminder: R Project Contributed Documentation Still Frozen

>>>>> Juan Telleria Ruiz de Aguirre >>>>> on Thu, 30 May 2019 18:46:29 +0200 writes: >Thank you Gabriel for valuable insights on the 64-bit integers topic. >In addition, my statement was wrong, as Python3 seems to have unlimited >(and variable) size integers. .... If you are interested in using unlimited size integers, you could use the

Thank you Gabriel for valuable insights on the 64-bit integers topic. In addition, my statement was wrong, as Python3 seems to have unlimited (and variable) size integers. Here is related CPython Code: https://github.com/python/cpython/blob/master/Objects/longobject.c Division between Int-32 and Int-64 seems to only happen in Python2. Best, Juan El mi?rcoles, 29 de mayo de 2019, Gabriel

Hi Juan, Comments inline. On Wed, May 29, 2019 at 12:48 PM Juan Telleria Ruiz de Aguirre < jtelleria.rproject at gmail.com> wrote: > Dear R Developers, > > There is an interesting issue related to "reticulate" R package which > discusses how to convert Python's non-32 bit integers to R, which has had > quite an exhaustive discussion: > >

Dear R Developers, There is an interesting issue related to "reticulate" R package which discusses how to convert Python's non-32 bit integers to R, which has had quite an exhaustive discussion: https://github.com/rstudio/reticulate/issues/323 Python seems to handle integers differently from R, and is dependant on the system arquitecture: On 32 bit systems uses 32-bit integers,

Thank you Frederick for your comments: They are really well justified. > I think a "forum" or bulletin board system would be a detraction from the project and a distraction for the project leaders. Users have Stack Exchange - it's better than any forum we could create, and it > takes care of itself. An excellent idea would be to add in the R Project Webpage a link to RSeek,

Dear R Developers, I started programming in R just last January, for which I read (, summarized and memorized) 2 incredible R Programming books: "R Cookbook" and "R Graphics Cookbook". However, I did before know how to program in MariaDB SQL language, and had submitted for their bug platform previously some bugs (https://jira.mariadb.org/projects/MDEV/issues), which is based

>>>>> Juan Telleria Ruiz de Aguirre >>>>> on Mon, 3 Jun 2019 06:50:17 +0200 writes: > Thank you Martin for giving to know and developing 'Rmpfr' library for > unlimited size integers (GNU C GMP) and arbitrary precision floats (GNU C > MPFR): > https://cran.r-project.org/package=Rmpfr > My question is: In the long term

I looks like you may have misunderstood my post so just to make sure: There will be no patch to R to support this. If this is something you want for yourself, then I have shown you how you can do it. You can put the code in a startup file if you like. If you want your students to have this, then you can prepare a startup file for them that does this. Best, luke On Thu, 21 May 2020, Juan

On 08/06/2017 6:31 AM, TELLERIA RUIZ DE AGUIRRE, JUAN wrote: > Dear R Developers, > > I started programming in R just last January, for which I read (, summarized and memorized) 2 incredible R Programming books: "R Cookbook" and "R Graphics Cookbook". > > However, I did before know how to program in MariaDB SQL language, and had submitted for their bug platform

Hi Juan, For bug reports to R, you should attempt to create a minimally-reproducible example, using only R's builtin facilities and not any other addon packages. Given your report, it's not clear whether the issue lies within renv or truly is caused by a change in R 4.0.0. Also note that you have not supplied a minimally reproducible example. If at all possible, you should be able to

Maybe a new Operator could be defined for a fast and easy double Comparison: `~~` `~~` <- function (e1, e2) all.equal(e1, e2) And document it properly.

You can get what you are asking for now in R 4.0.0 with globalCallingHandlers and using the packageConflictError object that is signaled. This should get you started: ``` options(conflicts.policy = "strict") packageConflictError handle_conflicts <- function(e) { cat(conditionMessage(e)) opt <- readline(prompt="1: mask.ok; 2: exclude. Choose: ") if (opt

Dear R Users, I have developed the following code for importing a series of zipped CSV by parallel computing. My problems are that: A) Some ZIP Files (Which contain CSVs inside) are corrupted, and cannot be opened. B) After executing parRapply I can only see the last.warning variable error, for knowing which CSV have failed in each node, but I cannot see all warnings, only 1 at a time. So: *

Dear Juan, I don't see what is the problem from your report. Please try to create a minimal but complete reproducible example that does not use the renv package. Perhaps you could use the R debugger (e.g. via options(error=recover)) to find out what is the argument that file.exists() has been called with. And then you could try just to call file.exists() directly with that argument to

Dear R Developers, I am having an issue with the renv package and R 4.0.1, which I suspect is related to base R and not the renv package itself, as with R 3.6.3 such an "error" does not appear. The error is raised by a file.exists() path, and path "C:\Users\J-tel\Documents", which in R 3.6.3 is read correctly, but in R 4.0.1 fails (Probably because of the "-"

The Xen Mercurial cheatsheet ( http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/hg-cheatsheet.txt ) says: <<<<<<<<<<<<< You can point a browser and this and use Hg''s web interface to view revision history, or use it as the nominated source when issuing "hg init" or "hg pull" commands. However, to avoid taxing the Mercurial

Hey if you know any rails cheatsheet link add it inot the follwing list, lets make a long list on Rails cheatsheet.... ;) 1) 2) 3) 4) . . . -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060103/a6eea2ac/attachment-0001.html

On Thu, Sep 20, 2018 at 11:46 AM Leo Lahti <leo.lahti at iki.fi> wrote: > > Time stamps are correct and my system time is correct. > > I am now tried to use Sys.setFileTime() to update time stamps as proposed. > This does not help. > > The windows and debian builds give different reports on the time stamp > issue. >

Thank you Martin for giving to know and developing 'Rmpfr' library for unlimited size integers (GNU C GMP) and arbitrary precision floats (GNU C MPFR): https://cran.r-project.org/package=Rmpfr My question is: In the long term (For R3.7.0 or R3.8.0): Does it have sense that CMP substitutes INTSXP, and MPFR substitutes REALSXP code? With this we would achieve that an integer is always an

Hi Tomas, I received a report about R 4.0.0 in the knitr package (https://github.com/yihui/knitr/issues/1840), and I think it is related to the issue here. I created a minimal reproducible example below: owd = setwd(tempdir()) z = 'K\u00e4sch.txt' file.create(z) list.files() file.exists(list.files()) setwd(owd) Output: > owd = setwd(tempdir()) > z = 'K\u00e4sch.txt' >