Closed barryrowlingson closed 2 years ago
I notice that the startup message printed by sf
differs between your two environments (with littler
, the sf_use_s2()
message is not printed.) This makes me wonder if the environment used by littler
has an older version of sf
, and possibly an older version of exactextractr
that does not understand the summarize_df
argument. Is this possible?
Yeah, weirdly r
has a .libPaths()
that includes a different set of paths to R
. Sorry I missed that.
Further, its my configuration that has a different .libPaths()
because I'd got a ~/.littler.r
startup file that mucked with the default. Going to bash head against desk for a bit now. Thanks.
Glad to see that the function signature inference is working!
For some reason
exact_extract
doesn't correctly recognise my summary function signature when running under thelittler
interpreter. Here's an example that runs fine when "source"d into an R session:producing:
It also runs okay via
R --vanilla < extract.R
andR CMD BATCH extract.R
. But withlittler
it doesn't correctly infer that the signature of the summary function in the second example is correct:If you've not seen
littler
before it is a package that provides a lightweight R interpreter designed for writing command-line scripts with quick startup and slightly modified command line argument passing.I've not looked at the source code for
exact_extract
to see how you do this inference so it may be due to something non-standard there or possibly something thatr
doesn't do for efficiency.At some point we may want to get the
littler
maintainers in on this, but maybe you can figure it out...B