Activate virtualenv after command prompt restart #284
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
My team got quite confused when they had to reopen the command line after doing the Heroku thingies and the next commands weren't working. It would be nice to have a reminder here because activating the virtualenv was ages ago :)
Activate virtualenv after command prompt restart
Although they already have done it once before, my girls were confused about what this command was supposed to do and they were a bit stuck. Maybe it's a good idea to make it clearer here.
| @@ -109,6 +109,8 @@ You need to install your Heroku toolbelt which you can find here (you can skip t | |||
|
|
|||
| > On Windows you also must run the following command to add Git and SSH to your command prompt's `PATH`: `setx PATH "%PATH%;C:\Program Files\Git\bin"`. Restart the command prompt program afterwards to enable the change. | |||
|
|
|||
| > After restarting your command prompt, don't forget to go to your `djangogirls` folder again and activate your virtualenv! (Hint: `myvenv\Scripts\activate`) | |||
There was a problem hiding this comment.
I think we should link to the relevant part of the tutorial here.
The problem is that the activate syntax is different between windows and linx/mac.
|
I will merge it and put a link to the appropriate chapter. Thank you! ❤️ |
aniav
added a commit
that referenced
this pull request
Mar 27, 2015
Activate virtualenv after command prompt restart
|
Thank you! Sorry I forgot to get back to this and fix it :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
My team got quite confused when they had to reopen the command line after doing the Heroku thingies and the next commands weren't working. It would be nice to have a reminder here because activating the virtualenv was ages ago :)