Claudio Jolowicz

> > breaking them apart into sections and section entries in a first pass, and using CYK only on the individual section entries > > In fact, this is already...

Thank you for working on this! I would prefer an approach where we forward pip options from the requirements file generated by Poetry. This has the advantage that we don't...

Hi @johnthagen you could use `poetry install` directly for this: ```python session.run_always("poetry", "install", "--no-root", "--no-dev", external=True) session.install("mypy") ``` When reusing virtualenvs, the `--no-dev` will cause mypy to be re-installed each...

> > When reusing virtualenvs, the --no-dev will cause `mypy` to be re-installed each time, unfortunately. > > Ah, that's too bad, I wonder if in practice (running type checking...

Thanks for the detailed report! Could this be related to #398 ? The repository config is currently not forwarded to pip. So you would need to explicitly [configure pip](https://pip.pypa.io/en/latest/topics/configuration/), for...

One thing to keep in mind: Currently, requirements files only live as long as their environment. If it's placed outside of environments, there is no mechanism to clean up a...

An implementation of this feature could use `nox.Session.cache_dir` introduced in Nox 2021.10.1.

There is a workaround, but it's a little bulky. You could use a [Dict variable]: ```json { "namespace": { "value": "abc" } } ``` Users can override this by entering...

As the dict variable workaround arguably doesn't lead to a great user experience, it may be better to treat some value special and document this in your template. For example,...

The issue with users being prompted for private dict variables (like your `_drPair`) was fixed in #1504, but it hasn't been released yet.