This changes requirements.txt to pin the django-haystack package to the v2.0.0 tag rather than depending on django_haystack/master to be at version 2.0.0-beta (it's at 2.1.1-dev right now).
I'm not a Python developer, but we were trying to get Councilmatic running at the @openlexington NDoCH today and pip was dying when the checked-out version (2.1.1-dev) didn't match the requirement (2.0.0-beta). I'm new to Councilmatic and haven't gotten the whole thing up and running yet, so I don't know if the move from the beta to the release causes any other problems.
This changes
requirements.txtto pin the django-haystack package to thev2.0.0tag rather than depending ondjango_haystack/masterto be at version 2.0.0-beta (it's at 2.1.1-dev right now).I'm not a Python developer, but we were trying to get Councilmatic running at the @openlexington NDoCH today and
pipwas dying when the checked-out version (2.1.1-dev) didn't match the requirement (2.0.0-beta). I'm new to Councilmatic and haven't gotten the whole thing up and running yet, so I don't know if the move from the beta to the release causes any other problems.