Havoc Pennington

Where did you mean exactly in anaconda-project? The situation as of 0.6.0 is that the platforms: field takes the same platforms as conda (minus noarch). In anaconda-project-lock.yml there are also...

(moving email realization onto the issue) Oh, I think I realized now you are talking about `unix:` and `win:` in the command definition. These were not intended to allow per-platform...

does entry points let someone bundle a plugin in their project? I don't know a lot about entry points but have some impression the setup.py thing is a little more...

the bulk of the work is to use the proxy whenever we make an http request I think, so I was thinking copy one of the two existing commands (`anaconda`,...

People generally would have to configure both so either might be fine? was going to see which looked easier!

This is partly addressed in #14 which will pass the conda output (or json events anyway) through, but leaving open for specifically a way to pass --verbose to conda.

Someone could push a logger that chains to other loggers if they wanted to, I guess? The rationale for verbose.py is to allow the CLI frontend to set a logger...

A tricky requirement we've come up with here is that we really want the plugin code to run in one of the project's environments, not in anaconda-project's environment. So that...

Implementation complexity: currently we use notebook/boken-specific knowledge before we "prepare" (create environments). This means if plugins are in those environments we create, something will have to change.

I don't think we'd want two ways to write plugins, we should do it the way we want to keep. Currently lean toward putting plugins in the anaconda-project process/environment because...