Return to Question

I recently posted a question in Stack Overflow, and after I got some replies I realized that the title I had chosen did not adequately describe the question I wanted to ask. I got several replies, including some that address to a tee what my botched title actually asks. My dilemma now is that, if on the one hand I accept one of these replies, I close off the opportunity to get an answer to what I really wanted to ask. On the other hand, changing the title of the question (and hence, in a way, the question being asked as well) seems shabby to those who took the time to reply.

I know from experience, both writing and replying to this sort of post, that choosing a good title is often tricky, and not easy to get right the first time. Therefore, I imagine that situations like this one are common in a site like Stack Overflow. What's considered the proper way to handle such a situation?

Thanks!

PS: FWIW, the post I'm referring to is stackoverflow.com/questions/7005323. For the title to really reflect what I'm asking, it would have to be something like, "How to salvage either the zip(*[iter(x)]*n) trick or the map(None, *[iter(x)]*n) trick when n % k > 0?" but this title seems to me way too long (isn't it?). Also, I'm sure it would be cryptic to most Python programmers, since these tricks are rarely mentioned in replies to questions on evenly "chunking" a list, but I think I will have to accept this: my question is arcane, so no accurate title could fail to be arcane as well. Therefore, for me now it's a toss up between the following titles:

How to salvage Python's zip(*[iter(x)]*n) trick when n % k > 0?
How to salvage Python's map(None, *[iter(x)]*n) trick when n % k > 0?

I recently posted a question in Stack Overflow, and after I got some replies I realized that the title I had chosen did not adequately describe the question I wanted to ask. I got several replies, including some that address to a tee what my botched title actually asks. My dilemma now is that, if on the one hand I accept one of these replies, I close off the opportunity to get an answer to what I really wanted to ask. On the other hand, changing the title of the question (and hence, in a way, the question being asked as well) seems shabby to those who took the time to reply.

I know from experience, both writing and replying to this sort of post, that choosing a good title is often tricky, and not easy to get right the first time. Therefore, I imagine that situations like this one are common in a site like Stack Overflow. What's considered the proper way to handle such a situation?

PS: For what it's worth, the post I'm referring to is stackoverflow.com/questions/7005323. For the title to really reflect what I'm asking, it would have to be something like, "How to salvage either the zip(*[iter(x)]*n) trick or the map(None, *[iter(x)]*n) trick when n % k > 0?" but this title seems to me way too long (isn't it?). Also, I'm sure it would be cryptic to most Python programmers, since these tricks are rarely mentioned in replies to questions on evenly "chunking" a list, but I think I will have to accept this: my question is arcane, so no accurate title could fail to be arcane as well. Therefore, for me now it's a toss up between the following titles:

How to salvage Python's zip(*[iter(x)]*n) trick when n % k > 0?
How to salvage Python's map(None, *[iter(x)]*n) trick when n % k > 0?

I recently posted a question in Stack Overflow, and after I got some replies I realized that the title I had chosen did not adequately describe the question I wanted to ask. I got several replies, including some that address to a tee what my botched title actually asks. My dilemma now is that, if on the one hand I accept one of these replies, I close off the opportunity to get an answer to what I really wanted to ask. On the other hand, changing the title of the question (and hence, in a way, the question being asked as well) seems shabby to those who took the time to reply.

I know from experience, both writing and replying to this sort of post, that choosing a good title is often tricky, and not easy to get right the first time. Therefore, I imagine that situations like this one are common in a site like Stack Overflow. What's considered the proper way to handle such a situation?

Thanks!

PS: FWIW, the post I'm referring to is stackoverflow.com/questions/7005323. For the title to really reflect what I'm asking, it would have to be something like, "How to salvage either the zip(*[iter(x)]*n) trick or the map(None, *[iter(x)]*n) trick when n % k > 0?" but this title seems to me way too long (isn't it?). Also, I'm sure it would be cryptic to most Python programmers, since these tricks are rarely mentioned in replies to questions on evenly "chunking" a list, but I think I will have to accept this: my question is arcane, so no accurate title could fail to be arcane as well. Therefore, for me now it's a toss up between the following titles:

How to salvage Python's zip(*[iter(x)]*n) trick when n % k > 0?
How to salvage Python's map(None, *[iter(x)]*n) trick when n % k > 0?

I recently posted a question in Stack Overflow, and after I got some replies I realized that the title I had chosen did not adequately describe the question I wanted to ask. I got several replies, including some that address to a tee what my botched title actually asks. My dilemma now is that, if on the one hand I accept one of these replies, I close off the opportunity to get an answer to what I really wanted to ask. On the other hand, changing the title of the question (and hence, in a way, the question being asked as well) seems shabby to those who took the time to reply.

I know from experience, both writing and replying to this sort of post, that choosing a good title is often tricky, and not easy to get right the first time. Therefore, I imagine that situations like this one are common in a site like Stack Overflow. What's considered the proper way to handle such a situation?

Thanks!

PS: FWIW, the post I'm referring to is stackoverflow.com/questions/7005323. For the title to really reflect what I'm asking, it would have to be something like, "How to salvage either the zip(*[iter(x)]*n) trick or the map(None, *[iter(x)]*n) trick when n % k > 0?" but this title seems to me way too long (isn't it?). Also, I'm sure it would be cryptic to most Python programmers, since these tricks are rarely mentioned in replies to questions on evenly "chunking" a list, but I think I will have to accept this: my question is arcane, so no accurate title could fail to be arcane as well. Therefore, for me now it's a toss up between the following titles:

How to salvage Python's zip(*[iter(x)]*n) trick when n % k > 0?
How to salvage Python's map(None, *[iter(x)]*n) trick when n % k > 0?

I recently posted a question in Stack Overflow, and after I got some replies I realized that the title I had chosen did not adequately describe the question I wanted to ask. I got several replies, including some that address to a tee what my botched title actually asks. My dilemma now is that, if on the one hand I accept one of these replies, I close off the opportunity to get an answer to what I really wanted to ask. On the other hand, changing the title of the question (and hence, in a way, the question being asked as well) seems shabby to those who took the time to reply.

I know from experience, both writing and replying to this sort of post, that choosing a good title is often tricky, and not easy to get right the first time. Therefore, I imagine that situations like this one are common in a site like Stack Overflow. What's considered the proper way to handle such a situation?

Thanks!

PS: FWIW, the post I'm referring to is Simple idiom to break an n-long list into k-long chunks, when n % k > 0?

For the title to really reflect what I'm asking, it would have to be something like, "How to salvage either the zip(*[iter(x)]*n) trick or the map(None, *[iter(x)]*n) trick when n % k > 0?" but this title seems to me way too long (isn't it?). Also, I'm sure it would be cryptic to most Python programmers, since these tricks are rarely mentioned in replies to questions on evenly "chunking" a list, but I think I will have to accept this: my question is arcane, so no accurate title could fail to be arcane as well. Therefore, for me now it's a toss up between the following titles:

How to salvage Python's zip(*[iter(x)]*n) trick when n % k > 0?
How to salvage Python's map(None, *[iter(x)]*n) trick when n % k > 0?

I recently posted a question in Stack Overflow, and after I got some replies I realized that the title I had chosen did not adequately describe the question I wanted to ask. I got several replies, including some that address to a tee what my botched title actually asks. My dilemma now is that, if on the one hand I accept one of these replies, I close off the opportunity to get an answer to what I really wanted to ask. On the other hand, changing the title of the question (and hence, in a way, the question being asked as well) seems shabby to those who took the time to reply.

I know from experience, both writing and replying to this sort of post, that choosing a good title is often tricky, and not easy to get right the first time. Therefore, I imagine that situations like this one are common in a site like Stack Overflow. What's considered the proper way to handle such a situation?

Thanks!

PS: FWIW, the post I'm referring to is stackoverflow.com/questions/7005323. For the title to really reflect what I'm asking, it would have to be something like, "How to salvage either the zip(*[iter(x)]*n) trick or the map(None, *[iter(x)]*n) trick when n % k > 0?" but this title seems to me way too long (isn't it?). Also, I'm sure it would be cryptic to most Python programmers, since these tricks are rarely mentioned in replies to questions on evenly "chunking" a list, but I think I will have to accept this: my question is arcane, so no accurate title could fail to be arcane as well. Therefore, for me now it's a toss up between the following titles:

How to salvage Python's zip(*[iter(x)]*n) trick when n % k > 0?
How to salvage Python's map(None, *[iter(x)]*n) trick when n % k > 0?