requirements.txt needs python-slugify

[aryamanarora]

Needs python-slugify as a dependency. Besides that, setting it up locally had no issues.

[nschneid]

Where is it used?

[aryamanarora]

ah so the real issue is that the dependencies for nert-nlp/django-categories should all be included in this repo too

[nschneid]

@lgessler Do you recall why we have a fork of django-categories?

[lgessler]

Basically, while we were working on #155, we found that django-categories's source code was directly committed to the repo at wiki/plugins/categories (cf. e.g. this commit), with custom changes we'd applied directly to this directory.

We decided that the cleanest thing to do was to fork django-categories, apply our changes downstream, and depend on it via a git submodule and a symlink. I can expand if you want.

Now that I'm thinking about it again though, a cleaner solution might be to get rid of the submodule and symlink and put git+git://github.com/nert-nlp/django-categories.git@master in this repo's requirements.txt. That should take care of the slugify dependency automatically.

[nschneid]

Sounds good to me

[lgessler]

BTW, if the django-categories dependency moves to requirements.txt, all references (in code and configuration) to wiki.plugins.categories will need to refer to categories instead. I don't think any other changes should be necessary.

[ablodge]

@lgessler How should the reference to wiki.plugins.categories.apps.CategoriesConfig be handled? It doesn't look like there is any reference to this in the django-categories repo. It gives me the following error:

django.core.exceptions.ImproperlyConfigured: Cannot import 'wiki.plugins.categories'. Check that 'categories.apps.CategoriesConfig.name' is correct

[lgessler]

I think what needs to happen is that CategoriesConfig.name needs to be assigned to just categories

[ablodge]

Can you merge nert-nlp/django-categories#1 ?