Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pip freeze #205

Merged
merged 2 commits into from
Nov 30, 2014
Merged

Pip freeze #205

merged 2 commits into from
Nov 30, 2014

Conversation

pozorvlak
Copy link
Contributor

Lots of our students got the impression that "pip freeze > filename" was the standard way of creating a file from the shell, which caused some really confusing problems later on. In particular, a surprising number of students created runtime.txt by running pip freeze > runtime.txt method, and then adding a Python version at the end. This caused endless confusion when Heroku told them that
(Django==1.7.1
dj-database-url==0.3.0
waitress==0.8.9
whitenoise==1.0.5
psycopg2==2.5.3
python-3.4.2) was not a runtime supported by the cedar-14 stack - at one point we had five coaches standing around one poor student trying to work out what had gone wrong!

I've tried to make it clearer that

  • the > operator performs output redirection
  • pip freeze isn't really a file-creation command
  • you create runtime.txt using your editor
  • only the python version should be included in runtime.txt.

I've also removed the word "simply" from this part of the instructions in line with the Coaching Guide.

Miles Gould added 2 commits November 30, 2014 13:20
Lots of our students got the impression that "pip freeze > filename" was
the standard way of creating a file from the shell, which caused some
really confusing problems later on!
We had a surprising number of students who created runtime.txt with the
`pip freeze > runtime.txt` method, and then added a Python version at
the end. This caused endless confusion when Heroku told them that
(Django==1.7.1
dj-database-url==0.3.0
waitress==0.8.9
whitenoise==1.0.5
psycopg2==2.5.3
python-3.4.2) was not a runtime supported by the cedar-14 stack - at one
point we had five coaches standing around one poor student trying to
work out what had gone wrong!

I've tried to make it clearer that

 - you create runtime.txt using your editor
 - only the python version should be included in the file

I've also removed the word "simply" from these instructions in line with
the Coaching Guide.
olasitarska added a commit that referenced this pull request Nov 30, 2014
@olasitarska olasitarska merged commit d151e2d into DjangoGirls:master Nov 30, 2014
@olasitarska
Copy link
Member

Very good change, thanks!

@pozorvlak
Copy link
Contributor Author

+1 to @d0ugal and @judy2k for finally working out what was going on!

@d0ugal
Copy link

d0ugal commented Nov 30, 2014

Thanks for updating this @pozorvlak - the errors seems so glaringly obvious now but it confused me and three other coaches for quite a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants