https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240820
rozhuk...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|Open |Closed
Resolution|--- |Overcome By Events
--- Comment #5 from rozhuk...@gmail.com ---
(In reply to Kai Knoblich from comment #4)
We are using FreeBSD + django in our product.
We was on django 1.08 and then try to migrate to 1.11 got this bug, that is why
9 months delay.
Now we are on 1.11 and I dont know how long we will use it.
It 100% reproduces in our project.
And this patch fix problem for us.
I'm trying to upstream all our patches to reduce support time in future.
(all new python ports from me)
https://github.com/django/django/pull/10733#issuecomment-518602957
>> My backport was rejected mainly for two reasons:
>> - Faulty analysis implying that it doesn't solve the problem (yes, it does)
>> - Django LTS "security only" support policy (this backport doesn't qualify
>> as a security issue)
Anyway, thanks for your time.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
