Heroku wants pylimbc in requirements.txt to bootstrap libmemcached about django-twoscoops-project HOT 9 CLOSED

The problem with including pylimbc in the bare requirements.txt file is that AFAIK it doesn't build on Windows. I'm going to ask @kennethreitz to weigh in on this one.

from django-twoscoops-project.

Try it.

from django-twoscoops-project.

It works when pylimbc is in the bare requirements.txt. When I push to heroku master, I can see this:

-----> Noticed pylibmc. Bootstrapping libmemcached.

This issue is not the end of the world, but it breaks the convention for requirements files.

from django-twoscoops-project.

@kennethreitz We brought one with us, just trying to make time for it.

@dogukantufekci How about putting pylibmc in the production.txt requirements file?

from django-twoscoops-project.

I tried to 'heroku push' a brand new app with pylibmc in production.txt and here is the message:

   Command /app/.heroku/python/bin/python -c "import setuptools;__file__='/tmp/pip-build-u22198/pylibmc/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-Om5uQB-record/install-record.txt --single-version-externally-managed failed with error code 1 in /tmp/pip-build-u22198/pylibmc
   Storing complete log in /app/.pip/pip.log

! Push rejected, failed to compile Python app

from django-twoscoops-project.

pylibmc is only supported if it is in the root requirements.txt.

from django-twoscoops-project.

@kennethreitz Really? Is this something Heroku will fix soon?

from django-twoscoops-project.

Considering the differences between Heroku and other PaaS, I wonder if it makes sense to break this project up into several smaller projects. Unfortunately, the differences are invariably at the settings and requirements level.

from django-twoscoops-project.

As much as we (me and@audreyr) would like to do this, realistically we don't have the time to do it right. Therefore we'll link to a maintained Heroku fork supported by members of the community.

I'll be pulling the Heroku material out of the main project. Nothing against Heroku (I like it a lot), it's just that customizing this to fit Heroku exactly is not ideal.

@dogukantufekci if you have a fork that does this that you'll maintain, we'll link to it from this main project.

from django-twoscoops-project.