Hi Colin,

On Sat, Nov 14, 2026 at 11:46:26PM +0000, Colin Watson wrote:
> On Sat, Nov 14, 2026 at 05:19:03PM +0100, Salvatore Bonaccorso wrote:
> > I'm raising this as first as RC level to explore the possiblity that
> > we can keep sqlparse out of forky or eventually remove. But at this
> > time there are a couple of problems considering that:
> [...]
> > # Broken Build-Depends:
> > pgcli: python3-sqlparse (0.3 >=)
> > python-django: python3-sqlparse
> > python-django-debug-toolbar: python3-sqlparse
> > python-pgspecial: python3-sqlparse
> > yoyo: python3-sqlparse
> > 
> > Dependency problem found.
> > 
> > so that would not be immediately possible. What do you think on the
> > the practical possibility to achieve that goal?
> 
> It seems extremely unlikely unless/until Django upstream stops depending on
> it.  At the moment it's used by all its DB backends.

Thanks for quickly following up on my question. So if you think it is
inapropriate under this cicumstances to have the bug RC, please *do*
downgrade.

The EOL statement and abadoning development should at least be on our
radar with respect of security support. If Django will continue to
heavily depend on it, there will likely be a solution :)

Regards,
Salvatore

Reply via email to