So I conveyed the issue somewhat poorly, apologies. We want to use the conda environment.yml to do two things. One is be our rtd build keystone. Two is be our way for developers who want to build the docs locally to do so with as few steps as possible. Something like `../.` was working locally as a way of getting whatever is currently installed to be relative to the location of the file. (see [this commit](https://github.com/jupyter/nbconvert/commit/f03ed5c1bfcfc2c27e7ecf864e880f682792fd85) but rtd choked on that.
Right now, the solution is to have readthedocs build it editably as an explicitly invoked command, and similarly we ask developers to do this explicitly (`pip install -e ../.`) after they've built and moved into the environment.
Dan I'm not sure how the file addressing works inside rtd containers. As Carol Said they can be tricky
New approach: put a minus (-) next to your name if you would NOTlike to audibly share progress during the meeting. The moderator will start at the top of the Hackpad and call out those without a minus next to their name.
Would like us to discuss this technical topic all together during this meeting
We've never had *good* support for lists on the CLI, though you could cram them into list literals, e.g. `--Class.list_trait="['x', 'y']"`. This paves the way for proper list aliases, etc., but it will be hard to do without breaking the old, clunky way.
I think i volunteered indirectly to be the lab rat for this experiment last Friday. Once there's a bit more than the vanilla cookiecutter, I'd like to sit down and try to add something as simple as a ... button? menu item? ... and see how far I get. I probably could use what's there, but I'm sure I'd start struggling as soon as I wanted to do more than console.log.