There was some very good news this week.
And while many people approved, applauded and celebrated it, there was no fireworks.
Because, well, the news from the City of Cape Town was that there would no longer be designated sites for fireworks this Guy Fawkes.
The reasoning was that: there was no longer a demand for it; policing the sites was a waste of resources; and the sheer volume of public complaints about
firecrackers.
Apparently, bassing klappertjies is already forbidden in terms of the Community Fire Safety By-law, but the City was nice enough to accommodate Guy Fawkes, Diwali and New Year’s Eve celebrations all these years.
But not anymore.
Of course, the announcement was music to the ears of animal lovers, parents fearing for their kids’ safety, and anyone hoping for a bit of peace and quiet on 5
November.
The Daily Voice polled readers and Facebook users, and almost no one was opposed to the “ban”.
The City could not have made a better decision, it seemed.
And they should have just given themselves a lekker pat on the back.
But then they got drawn into a pedantic, red tape debate.
Mayoral Committee Member for Safety and Security, JP Smith, later felt the need to point out that it was not a “ban” at all.
While klappertjies contravene local by-laws, only national government could make a call to criminalise it.
“We indicated that while there have for years been calls to ban fireworks outright, the City does not have the power to do so,” Smith said.
“That this translated into a ‘ban’ on fireworks is disappointing, but not surprising.”
FIGHTING FIRE: JP Smith
He added that to accommodate Hindus wanting to celebrate Diwali, the City would make the parking lot at Athlone Stadium available on 27 October.
He reiterated that organised fireworks displays can still be applied for.
And just like that, Smith’s klappertjie ban backfired.
And he went from being decisive and clear, to indecisive and ambiguous.