Date: Wed, 22 Apr 2020 08:31:04 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 240820] www/py-django111: SQLite backend broken after 3.26 Message-ID: <bug-240820-21822-GWkAMaOa2A@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-240820-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-240820-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240820 rozhuk.im@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |Overcome By Events --- Comment #5 from rozhuk.im@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.=20 (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 qua= lify as a security issue) Anyway, thanks for your time. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240820-21822-GWkAMaOa2A>