Doc request: Guidance request about virtualenv settings for child packages, and what other commands are affected.

[gregg-maiven]

Love this project, and how much of the friction it removes!

Two main questions:

1. What should the various virtualenv settings be for the child proejcts. Should they create virtualenvs or not?

2. poetry run uses the monorepo root.... with mixed effects.

This is causing my some issues with python run ipython and similar.

Thanks!

[ag14774]

Good question and that is a good point that we should add some documentation on that.

1. By default poetry will indeed have the side effect of creating a virtualenv for the child project if one does not exist, but it will not use it. This is not necessary. You can stop this behavior by creating a poetry.toml file in the root of the child project with:

[virtualenvs]
create = false

That being said, even with this, poetry will give you a warning 'Not creating virtualenv' because of this configuration but then the plugin proceeds to create a virtualenv for the monorepo root. I have not found a way to suppress this warning yet. Note that this setting is optional. You can also let poetry create a virtual env but it will still use the shared env from the root of the monorepo.

2. The side-effect I imagine is that it creates a virtualenv for the child project. Are there any other effects you have observed?