3 ms·
I can't agree more with you. That's the one and only reason I'll stick to the 1.11 version. Garanty of compatibility between Django and ALL my external package
by bluewalt 9y ago
I can't agree more with you.
That's the one and only reason I'll stick to the 1.11 version.
Garanty of compatibility between Django and ALL my external packages is a lot more valuable that a responsive admin panel and a new syntax for urls.
I would love "important" (yeah it's opiniated) packages move to the official Django repo (like Channels), to help reduce this risk when migrating.
It's actually surprising how often I can't find the compatibility information of a Django package.
- rtpg 9y agoI've had decent luck for the most part, but it only takes one package. I would love to see someone start on a combination of `pyup` and some "maintenance fee" for projects that are found in ones `requirements.txt`. For a monthly fee you can make sure that at least someone is checking to see that your Django dependencies are being kept up to date as time moves forward. The pitch being "get an extra maintenance developer for a fraction of the cost".
- collinmanderson 9y ago(Channels is in the Django Github _organization_, separate repo.) Though, in theory, I don't think there's any actual difference in support having it under the Django _organization_.