Q: Is crispy-forms getting deprecated? (A: No)

I am happily using crispy-forms: I have created my own template pack to render Bootstrap 4 custom forms and built some custom form layout. Everything is DRY and simple.

But now Django 1.11 has landed and with it comes the ability to customize widget templates. I am a little concerned about the future of crispy-forms in relation with these new features (I am questioning myself: is crispy-forms still worth it?). Furthermore, almost a year has passed since the last version update.

I am not criticising the work of the developers (everyone has other stuff to do) but since I am heavily using it I am asking if there are any plans for the future in relation with Django 1.11.

[carltongibson]

@bluesurfer Good question.

At this stage there’s no plan to wind up the project. A new release for Django 2.0 will come shortly. There’s been lots of little additions but no great changes requiring a new release in the meantime. (If people want they can install from GitHub quite easily.)

If template sets for Django get released then maybe Crispy Forms will no longer be needed. (But Layouts still offer a lot even then.)

With regard to Bootstrap 4 in particular, it’s a bit difficult following a moving target — I don’t use it myself — so all contributions to make the templates there great are appreciated. We started well but enthusiasm from the community dropped as each pre-release version brought breaking changes: the consensus seemed to be to wait until BS4 was finalised before doing too much more work. I’m very happy to have input on the BS4 templates from anyone who can step up there.

[durdenk]

I never needed to modify crispy form’s templates, the thing makes crispy forms best is the nested object layouts. I dont understand why django’s template system would make this project deprecated.

I want to thank to conributors here, I’m not accustomed python and git enough to contribute right now, but I hope to contribute to project in the future.