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

"No module named pip" error on push to heroku #9

Closed
lovesh opened this issue Mar 6, 2015 · 3 comments
Closed

"No module named pip" error on push to heroku #9

lovesh opened this issue Mar 6, 2015 · 3 comments

Comments

@lovesh
Copy link

lovesh commented Mar 6, 2015

When i push to heroku the push gets rejected with this error message

-----> Fetching custom git buildpack... done
-----> Pelican app detected
-----> Installing Python (python-3.4.2)
-----> Ensure pip
Ignoring ensurepip failure: pip 1.5.6 requires SSL/TLS
-----> Installing Pelican
/app/tmp/cache/python-3.4.2/bin/python: No module named pip

 !     Push rejected, failed to compile Pelican app
@lovesh lovesh changed the title No module named pip error push to heroku "No module named pip" error push to heroku Mar 6, 2015
@lovesh lovesh changed the title "No module named pip" error push to heroku "No module named pip" error on push to heroku Mar 6, 2015
@AdamWagner
Copy link

+1

Also having this issue. Many Google searches and attempts later, and can't find a way around this one. Does the buildpack need updated?

@atkailash
Copy link

I figured out the problem, at least for me. My app stack was set for Cedar-14 automatically, but it seems the buildpack is set for cedar. When the stack for the application is set to cedar (heroku stack:set cedar <appname>), it works fine. I'm trying to figure out how to fix it right now, but can't find a whole lot of helpful documentation to see specifically

@atkailash
Copy link

Well, that was simple! Changed the variable in "build" to "cedar-14" and worked just fine. Submitting pull request now.

Pull request #10 fixes, I neglected to mention it goes to this issue in it.

@kylef kylef closed this as completed May 2, 2015
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