You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
People contributed to the original ticket: @rutsky
Ticket created on: Mar 14 2016
Ticket last modified on: Jun 07 2016
Currently we create virtualenv and do all command from inside of virtualenv, which sounds horrible to me: virtualenv should be used as opaque directory with minimal usage of internal structure.
Also these commands doesn't work on windows, since pip and other scripts are inside Scripts/ directory, not bin/.
I suggest to rewrite docs to use virtualenv activation as it was done in eight branch.
The text was updated successfully, but these errors were encountered:
This ticket is a migrated Trac ticket 3483
People contributed to the original ticket: @rutsky
Ticket created on:
Mar 14 2016
Ticket last modified on:
Jun 07 2016
Currently we create virtualenv and do all command from inside of virtualenv, which sounds horrible to me: virtualenv should be used as opaque directory with minimal usage of internal structure.
Also these commands doesn't work on windows, since
pip
and other scripts are insideScripts/
directory, notbin/
.I suggest to rewrite docs to use virtualenv activation as it was done in eight branch.
The text was updated successfully, but these errors were encountered: