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

file encoding #180

Closed
spooky opened this issue Nov 11, 2014 · 5 comments
Closed

file encoding #180

spooky opened this issue Nov 11, 2014 · 5 comments

Comments

@spooky
Copy link

spooky commented Nov 11, 2014

on windows, depending in cmd or powershell is used when generating requirements.txt by running

pip freeze > requirements.txt

sometimes leads to a situation where windows1250 encoding is used. that generates problems with heroku further on.

@bmispelon
Copy link
Contributor

Interesting. What kind of problems does this create with Heroku?

@MattBlack85
Copy link
Contributor

we had a similar problem with runtime.txt, file created with gedit didn't allow for a successful push to heroku, girls got error regarding python version not supported on the cedar. Changing the file with another one solved this issue

@bmispelon
Copy link
Contributor

@MattBlack85 This particular problem is actually caused by windows line endings instead of unix ones. It can be fixed simply by only having one line in the file.

@spooky
Copy link
Author

spooky commented Nov 11, 2014

@bmispelon sorry, I don't have the error message :/

@olasitarska
Copy link
Member

As this error is not clear, I'm going to close this. Please re-open if this comes up again.

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

No branches or pull requests

4 participants