What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 131 Stack Exchange communities.

This question already has an answer here:

I know that there has been much discussion about the new close reasons, and I agree with them fully.. But now there is a problem with certain questions... I will give an example:

all(x = y): bool object not iterable - SOLVED

This question is clearly something that would fit into the old "Too Localized" close reason.

The OP answered his own question, and the answer seems to be that he made a mistake with his imports....

Under the new close reasons - how should this question be close?

share|improve this question

marked as duplicate by Bart, hims056, Lucifer, Shadow Wizard, ben is uǝq backwards Jun 27 '13 at 8:42

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

    
Check under "off topic"--a lot of reasons were moved around. –  simchona Jun 27 '13 at 7:58

2 Answers 2

up vote 2 down vote accepted

Too localized was misused because it was too opinion based. Now you have to give a close reason based on analytical thinking and not only emotions.

Questions concerning problems with code you've written must describe the specific problem and include valid code to reproduce it.

seems to be good. You should describe the problem and include valid code, and not include invalid code and write you have a problem.

Questions must demonstrate a minimal understanding of the problem being solved. Tell us what you've tried to do, why it didn't work, and how it should work

and than one would be perfect when it's clear that the OP doesn't understand the code (s)he is posting.

share|improve this answer
1  
Maybe those descriptions should be slightly expanded. –  Inbar Rose Jun 27 '13 at 8:32
    
Yes, I for me all of them are not very clear. I'm afraid they could be as much misunderstood as too localized... –  РСТȢѸФХѾЦЧШЩЪЫЬѢѤЮѦѪѨѬѠѺѮѰѲѴ Jun 27 '13 at 8:35

It probably should not be closed under any of the predefined reasons, since none of them apply to the specific question. If you really want to close it, you can chose Off topic --> Other and add an explanation why you think that it should be closed.

If you chose the "Other" reason, it would be better to use one of the existing reasons listed here. If a reason is chosen enough times, the moderators will consider to add it to the predefined ones.

share|improve this answer
2  
Well. It is pretty much some one dumping their "not-working" code into StackOverflow and asking for help.. then solving it by realizing he forgot to import something.. I really don't see how that should stay open? –  Inbar Rose Jun 27 '13 at 8:02
2  
Typo-questions, as they're commonly called, are common enough that they SHOULD warrant their own close-reason under off-topic or wherever - not "other". –  J. Steen Jun 27 '13 at 8:10
3  
I'm sorry but "There is no close reason for it, so it shouldn't be closed." is simply wrong. It just means that the new close reasons are causing way more trouble than they should. –  user98085 Jun 27 '13 at 8:11
    
@FEichinger The moderators are monitoring the custom close reasons. (can't find the link to the relevant question at the moment). If a reason is selected frequently enough, they will add it to the predefined ones. –  user000001 Jun 27 '13 at 8:17
    
I'm well aware of that. My comment was in response to the original revision of your post, which was worded differently. –  user98085 Jun 27 '13 at 9:10
    
Oops I added the wrong ping :). My previous comment was for @J.Steen –  user000001 Jun 27 '13 at 9:29
    
@FEichinger Yea I changed my mind on that and voted to close the question. –  user000001 Jun 27 '13 at 9:31

Not the answer you're looking for? Browse other questions tagged .