extirpate (or update) fetch calls in Modeling

[nicholasjhorton]

No description provided.

[rpruim]

All that needs doing is an additional require(fetch). Just make sure that it comes after mosaic.

Hmm.. We could have the fetch functions in mosaic check whether fetch is available and use it rather than print the error message. That would avoid the issue of loading packages in the wrong order and hide the error message from people with both packages loaded.

[nicholasjhorton]

I'd prefer to make it go away. Having people have to install multiple packages or refer to external things that we don't think are germane violates "Less Volume, More Creativity" in terms of complexity.

Just my $0.02,

Nick

On May 26, 2015, at 6:43 PM, Randall Pruim [email protected] wrote:

All that needs doing is an additional require(fetch). Just make sure that it comes after mosaic.

Hmm.. We could have the fetch functions in mosaic check whether fetch is available and use it rather than print the error message. That would avoid the issue of loading packages in the wrong order and hide the error message from people with both packages loaded.

—
Reply to this email directly or view it on GitHub.

Nicholas Horton
Professor of Statistics
Department of Mathematics and Statistics, Amherst College
Box 2239, 31 Quadrangle Dr
Amherst, MA 01002-5000
https://www.amherst.edu/people/facstaff/nhorton

[rpruim]

There is no need for the fetchData() function to "go away". People who want it can get it using fetch. That maintains a form of backward compatibility.

But I think we should not use it in our stuff. Not sure which sense of "go away" you intended.

I think the biggest issue will be some of Danny's things where IIRC he has used it much more heavily than I have.