Spotter-Cluster/Spotter-VM
2
0
Fork 0
Code Issues 78 Pull Requests Actions Packages Projects Releases Wiki Activity

Add a note about Pandora celery workaround

Browse Source
This commit is contained in:
Disassembler 2020-06-21 18:54:05 +02:00
parent 3839eddb60
commit 09b7ce481f
No known key found for this signature in database
GPG Key ID: 524BD33A0EE29499
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/applications/pandora.rst
View File

@ -22,4 +22,4 @@ Czech localtization for Pan.do/ra currently exists only in SpotterVM repository.
Python 3.8 compatibility Python 3.8 compatibility
------------------------ ------------------------
Pandora doesn't work well under python 3.8. Specifically, the database migration won't pass. This is caused by old version of Django, which doesn't play well with the new version of psycopg2 (see https://github.com/divio/django-cms/issues/6672), however older version of psycopg2 (2.7.7 as recommended in the linked issue) can't be installed on python3.8 as it uses some undocumented feature unsupported in python3.8 (https://github.com/psycopg/psycopg2/issues/854). The way out of this for Pandora would likely be to eventually bump the required version of Django to version 2.2+ which works well with psycopg2 2.8+. Pan.do/ra maintainer is aware of this, but it's not a simple task. For the time being, Pandora is stuck on python 3.7 provided by Alpine 3.10. Pandora uses Celery message broker, however depends on a version with known incompatibility with python 3.8, see https://github.com/celery/celery/issues/5761. This can be worked around by setting environment variable ``COLUMNS`` to value ``80`` prior to launching the celery process. The affected services run by container's s6 daemon supervisor are currently configured to use this workaround.