Skip to main content
Meta Stack Exchange

Return to Question

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

Concrete example:

Despite almost identical titles (and the same user task -- send email) the questions are about different issues underneath: the first question might be about shadowing Python stdlib module due to filename conflict. The second -- about ssl error.

Should such questions be merged (one closed as a duplicate of another) or should they be kept separate?

Concrete example:

Despite almost identical titles (and the same user task -- send email) the questions are about different issues underneath: the first question might be about shadowing Python stdlib module due to filename conflict. The second -- about ssl error.

Should such questions be merged (one closed as a duplicate of another) or should they be kept separate?

Concrete example:

Despite almost identical titles (and the same user task -- send email) the questions are about different issues underneath: the first question might be about shadowing Python stdlib module due to filename conflict. The second -- about ssl error.

Should such questions be merged (one closed as a duplicate of another) or should they be kept separate?

Post Closed as "Duplicate" by gnat, Martijn Pieters, Josh Crozier, Cjxcz Odjcayrwl, Himanshu
Source Link
jfs
jfs
  • 2.4k
  • 16
  • 20

What to do with debugging questions when fixing one problem exposes another? Should a separate question be asked?

Concrete example:

Despite almost identical titles (and the same user task -- send email) the questions are about different issues underneath: the first question might be about shadowing Python stdlib module due to filename conflict. The second -- about ssl error.

Should such questions be merged (one closed as a duplicate of another) or should they be kept separate?