Issue #122 resolved

first activation of venv inconsistent when using "mkvirtaulenv -a project_path"

Mike Fogel
created an issue

When the -a project_path flag is used with mkvirtualenv, the first time the virtualenv is activated the .project link has not been created yet. On all subsequent activations, it'll be there.

This inconsistent state means that any pre/post activation hooks can't rely on the existence of this .project link.

Attached is a patch that fixes this issue - makes the .project available at every activation, even the first one.

Apologies for not catching this before submitting those pull requests! Thanks.

Comments (3)

  1. Log in to comment