A long time ago the question avoiding Python multiline string indentation was asked. The question was well received with a score of 66 and 16 favourites. It was even answered by one of our previous mods (who deleted their answer).
However yesterday it popped up in the close queue where five out of five users voted to close the question. Later that day it was added to the reopen queue, one user selected to keep it closed, where a moderator mod-hammered it open, with an edit. This edit was noticed by Duga, and posted to chat. Where I noticed the question, agreed with the closure and voted to close it as broken, which started another review in the close queue. This lead to a user voting to close the question, and a different moderator mod-hammering to leave the question open.
It has also been reviewed in the past where all (3) reviewers in the queue elected to leave it open.
And has been reviewed again where 2 voted to close and 3 voted to leave it open.
In total it received:
- 9 Votes to close
- 1 Vote to keep closed
- 1 Vote to reopen
- 7 Votes to leave open
And so the votes so far have been:
- 9 People have voted in favour for the question to be closed.
- 7 People have counter-voted those close-votes to reopen or leave open the question.
To note the close reasons have changed since the question was originally posted. Here describes most of the story of the close reasons. Where, if you have 10k rep, you can also see all the changes to the close reasons here. And so we can see that when the question was posted it was when we had our previous close reasons:
- Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. After the question has been edited to contain working code, we will consider reopening it.
- Questions must involve real code that you own or maintain. Pseudocode, hypothetical code, or stub code should be replaced by a concrete implementation. Questions seeking an explanation of someone else's code are also of-topic.
- Questions must include the code to be reviewed. Links to code hosted on third-party sites are permissible, but the most relevant excerpts must be embedded in the question itself.
Where the broken code reason hasn't changed much:
Code not implemented or not working as intended: Code Review is a community where programmers peer-review your working code to address issues such as security, maintainability, performance, and scalability. We require that the code be working correctly, to the best of the author's knowledge, before proceeding with a review.
It seems like a lot of users think this question should be closed. However moderators have been mod-hammering it open.
Is the question on-topic or off-topic?