Feature #6712

Specify Django version

Added by Evgeny Novikov over 4 years ago. Updated about 1 year ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Published in build:


It is well known that Bridge can be run just with several particular versions of Django. Deployment scripts should take care about that.



Updated by Evgeny Novikov about 3 years ago

  • Priority changed from Normal to Urgent

Let's shed light on this at last. It will be much better if everybody will be bound to use some particular version of Django rather than rely upon a variety of them should behave properly and in the same way.


Updated by Evgeny Novikov almost 3 years ago

  • Status changed from New to Rejected
  • Assignee deleted (Vladimir Gratinskiy)
  • Priority changed from Urgent to High

Eventually I consider this issue strange since similar requirements should be specified for all used libraries and tools but there aren't corresponding feature requests.


Updated by Evgeny Novikov about 1 year ago

  • Target version set to 3.0
  • Priority changed from High to Immediate
  • Assignee set to Evgeny Novikov
  • Status changed from Rejected to Open
  • Category changed from Documentation to Deployment
  • Description updated (diff)
  • Subject changed from Minimal and maximum version of Django to Specify Django version

I re-opened the issue as yesterday Django 2.2 was released and at least Bridge migrations started to fail with it. Everybody, let's use Django 2.1.7 that definitely works until explicit update of supported version in Bridge.


Updated by Evgeny Novikov about 1 year ago

  • Status changed from Open to Resolved

I fixed this in branch deploy-linux-3.14-build-base.


Updated by Evgeny Novikov about 1 year ago

  • Status changed from Resolved to Closed

Tests passed, so, I merged the branch to master in commmit:afaaf5f.

Vladimir Gratinskiy, please, update Bridge to new versions of Django in separate branches and via explicit new features at Forge.

Also available in: Atom PDF