Tomasz Kalinowski

Ok, I have a tentative fix in reticulate. A recent refactor of `py_to_r()/r_to_py()` and the `PyObjectRef` class in reticulate made this change much easier than it would have been otherwise....

Convenience mostly. An attribute is how Python callables keep a reference to the environment with the external pointer; making conditions consistent with that keeps the reticulate internals simpler and lets...

Easy workaround with `#' @exportS3Method base::all.equal`

Perhaps roxygen2 should emit a warning in this case, asking users to resolve the ambiguity?

Instead of moving away from `tf.data`, a much easier goal is to make `keras-hub` work well with `tensorflow-cpu`. `tensorflow-cpu` should not introduce conflicts with any parts of jax/torch/cuda generally. Unfortunately,...

I'm guessing the current incompatibility between `tensorflow-text` (ergo, `keras-hub`) and `tensorflow-cpu` is a known issue; I just noticed that `tensorflow-cpu` is pinned to `~=2.18.1` in `keras-team/keras` CI, which doesn't have...

@SamEdwardes I think `RETICULATE_PYTHON` should point to a python binary, not a venv root. e.g., `.venv/bin/python`.

Thanks for pushing this along! > ```r > reticulate::virtualenv_create("./.venv", "/opt/homebrew/bin/python3.13") > > # Configure renv to use the virtual environment > renv::use_python("./.venv/bin/python") > > Sys.setenv( > RETICULATE_USE_MANAGED_VENV = "no", >...