DemARK build recipes

[sbenthall]

There are a number of DemARKs that are essentially documentation.
These should be moved into the examples/ directory.

#442 (comment)

(work on this after #442 is merged)

[sbenthall]

Many of these should not go in the examples directory. Need a judgment on this.
#442 (comment)

[sbenthall]

This task is made less straightforward by the fact that DemARKS may not all work as expected. See:
econ-ark/DemARK#82

[sbenthall]

Specifically, DemARK .py code seems to run as expected with python, but not always with ipython.
Before moving this code into examples/ we should settle on the requirements for example/ code.

[llorracc]

This seems like a fortuitous time for this point to come to the surface, since our conv later today with Andrij needs to be in large part about this issue of requirements. Mridul, could I ask you to draft a Markdown document that we can all look at somewhere, with links to what we are currently doing with out postBuild files for REMARKs and DemARKs and with a summary of the issues we have encountered? Specifically, as I understand it we are thinking of handling things by having a proposed "default" /binder folder for REMARKs DemARKs and then saying that if a particular REMARK or DemARK needs anything extra it will have to "pip" or "conda" install that extra stuff explicitly. If you agree that this is a good description of our previous conversations, then could you cobble together proposed template REMARK and DemARK /binder files and at least one example of a DemARK and a REMARK that will install something extra beyond the default? I think that would make the conv with Andrij much more effective.

…

On Mon, Jan 6, 2020 at 11:22 AM Sebastian Benthall ***@***.***> wrote: Specifically, DemARK .py code seems to run as expected with python, but not always with ipython. Before moving this code into examples/ we should settle on the requirements for example/ code. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#459?email_source=notifications&email_token=AAKCK74HABP43Z3TXHHLEV3Q4NLERA5CNFSM4JZ73T52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIF6GXI#issuecomment-571204445>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKCK77K2M2J2UDPSV5HIITQ4NLERANCNFSM4JZ73T5Q> .

-- - Chris Carroll

[MridulS]

The build recipes for binder of REMARKs are handled automatically as they are supposed to be individual repos and we can create custom recipes as we wish for a repo, which builds on top of standard dependencies of HARK.

For DemARKs we decided to have synced up pinned releases with a HARK release, so there will be a 0.10.7 DemARK release with a 0.10.7 HARK release, and the binder build recipe will be the union of all demarks imports.