python - Pushing app to Heroku failed because of django_comments -


i tried push project heroku , failed because couldn't find django_comments. here log:

-----> using set buildpack heroku/python -----> python app detected      $ pip install -r requirements.txt      $ python manage.py collectstatic --noinput        traceback (most recent call last):          file "manage.py", line 10, in <module>            execute_from_command_line(sys.argv)          file "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/__init__.py", line 353, in execute_from_command_line            utility.execute()          file "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/__init__.py", line 327, in execute            django.setup()          file "/app/.heroku/python/lib/python2.7/site-packages/django/__init__.py", line 18, in setup            apps.populate(settings.installed_apps)          file "/app/.heroku/python/lib/python2.7/site-packages/django/apps/registry.py", line 85, in populate            app_config = appconfig.create(entry)          file "/app/.heroku/python/lib/python2.7/site-packages/django/apps/config.py", line 90, in create            module = import_module(entry)          file "/app/.heroku/python/lib/python2.7/importlib/__init__.py", line 37, in import_module            __import__(name)        importerror: no module named django_comments  !     error while running '$ python manage.py collectstatic --noinput'.        see traceback above details.        may need update application code resolve error.        or, can disable collectstatic application:           $ heroku config:set disable_collectstatic=1        https://devcenter.heroku.com/articles/django-assets ****** collectstatic environment variables:        cplus_include_path=/app/.heroku/vendor/include:/app/.heroku/vendor/include:/app/.heroku/python/include:        source_version=9698848ab6d9bab7f8c8e2181eb933f2619341e9        profile_path=/app/.profile.d/python.sh        debug_collectstatic=1        library_path=/app/.heroku/vendor/lib:/app/.heroku/vendor/lib:/app/.heroku/python/lib:        cache_dir=/app/tmp/cache        pythonunbuffered=1        heroku_postgresql_aqua_url=postgres://wlxiltlrxwplzs:xdqanl2tlh_ndd_p_huse2jucm@ec2-54-243-201-3.compute-1.amazonaws.com:5432/d6t4rugnogngm3        pyhonhome=/app/.heroku/python        ld_library_path=/app/.heroku/vendor/lib:/app/.heroku/vendor/lib:/app/.heroku/python/lib:        bin_dir=/app/tmp/buildpacks/python/bin        path=/app/.heroku/python/bin:/app/.heroku/vendor/bin::/usr/local/bin:/app/bin:/app/vendor/bundle/bin:/app/vendor/bundle/ruby/2.3.0/bin:/usr/local/bin:/usr/bin:/bin:/tmp/codon/vendor/bin:/app/tmp/buildpacks/python/vendor/bpwatch:/app/tmp/buildpacks/python/vendor/pip-pop        recommended_python_version=python-2.7.11        c_include_path=/app/.heroku/vendor/include:/app/.heroku/vendor/include:/app/.heroku/python/include:        enable_collectstatic=1        pwd=/app        log_file=/tmp/fifo20160525-3-183u9i6        lang=en_us.utf-8        stack=cedar-14        shlvl=3        request_id=8504b0c1-bbd2-4360-ae76-7dfc10b78046        home=/app        bpwatch_store_path=/app/tmp/cache/bpwatch.json        pythonpath=/app/        build_dir=/app        warnings_log=/tmp/tmp.ixuqyzgyw1        heroku_postgresql_navy_url=postgres://ulkvhxkyxdewvx:psgxzee3otdwghgap5jinygdpw@ec2-54-243-200-159.compute-1.amazonaws.com:5432/d77uogldogo1op        user_log_file=/tmp/fifo20160525-3-yjcxuf        pkg_config_path=/app/.heroku/vendor/lib/pkgconfig:/app/.heroku/vendor/lib/pkgconfig:/app/.heroku/vendor/lib/pkg-config:/app/.heroku/vendor/lib/pkg-config:/app/.heroku/python/lib/pkg-config:        database_url=postgres://hvjyqvblijhpsk:gx4wjqn8bjshovwrb39nayadza@ec2-23-21-255-14.compute-1.amazonaws.com:5432/d2j3l0bc45qakf        _=/usr/bin/env  !     push rejected, failed compile python app`

this requiremenst.txt:

dj-database-url==0.4.0  django==1.9.2  gunicorn==19.4.5  psycopg2==2.6.1  whitenoise==2.0.6

the pypi package name django_comments module django-contrib-comments. add following line requirements.txt:

django-contrib-comments

or, specific version number, such as:

django-contrib-comments==1.7.1

-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more