Resolve circular dep when installing gunicorn in venv #223
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The anchor pattern now requires python::config to happen before creating virtual envs. If gunicorn is installed in the virtual env, it can not be started before the virtual env is created. But the service is declared in python::config.
That looks something like this:
The declaration that causes this is:
If I don't require the
Python::Virtualenv
in myPython::Gunicorn
, gunicorn won't be able to start.Note that this doesn't re-introduce #215, since the virtual env is still created after the packages are installed.