Reported by a Herkou user, not yet verified by myself. Would be nice to find a way to reproduce without RubyPython... ``` heroku run console --app myapp-cedar Running console attached to terminal... up, run.7 irb(main):001:0> require 'rubypython' => true irb(main):002:0> RubyPython.start LoadError: Could not open library '/usr/local/lib/libpython2.7.a': /usr/local/lib/libpython2.7.a: invalid ELF header ```
Activity
fdr commentedon Oct 20, 2011
What's funny is I used readelf immediately after and it seemed okay....maybe?
asenchi commentedon Oct 25, 2011
I looked at this also. I couldn't find anything wrong with it either. We may want to talk to a Python dev.
rwdaigle commentedon Feb 20, 2012
I've had success specifying
and locking RubyPython to v0.5.1 in my
Gemfile.Suggested in this thread: pygments/pygments.rb#10
kennethreitz commentedon Feb 21, 2012
Safe to close? This isn't related to the Python buildpack anyway.
rwdaigle commentedon Feb 21, 2012
Perhaps transfer to the appropriate project/team?
It's still an issue.
kennethreitz commentedon Feb 21, 2012
Would it be runtime?
The Python buildpack won't be relying on the stack-image's Python in the near future.
Merge pull request heroku#5 from chrisleishman/npm_prune
Use the namespace geodjango_ for our lib steps