10
\$\begingroup\$

I was checking out the tags today, and I think we could clean up a couple tags. For all three suggestions, I think a synonym should suffice. I was unable to propose them, as version-specific tags can only be proposed by moderators.

I ran into a similar meta request for to be synonymized, and this is just an expansion.

For all three, I really agree with this clean up proposal.

Note: I chose not because it's the most recent language update. I'm not sure what to do about . Suggestions?

\$\endgroup\$
  • \$\begingroup\$ I see no reason python2.7 shouldn't be synonymized if python3 is. \$\endgroup\$ – RubberDuck Jul 31 '14 at 4:29
  • 1
    \$\begingroup\$ I agree with ckuhn203. If anything, the newest version should be un-synonymized at least until a newer version comes out. But I don't like version-specific tags. \$\endgroup\$ – nhgrif Jul 31 '14 at 22:20
8
\$\begingroup\$

I would caution against making a sweeping decision that applies to all language-version tags.

Some languages, like , are conservative, and introduce new features with very few incompatible changes between major versions. It makes sense to abolish .

Other languages are more innovative. For example, has introduced breaking changes from Python 2 to 3. Sometimes, it is immediately clear from context whether code targets Python 2 or Python 3, sometimes it is not obvious, and some code runs flawlessly on both. Therefore, the and tags are situationally useful, if the author wants to specify the language version. Therefore, for Python at least, I think that the language-version tags should be used at the discretion of the author or editor of each question — the tags should be neither mandatory, synonymized, nor merged.

\$\endgroup\$
  • 3
    \$\begingroup\$ Would it be fair to make this tags similar as well as eliminate the subversion? [python-2.x], [python-3.x]? Or are there drastic changes between subversions of Python that would warrant the subversions having their own tags as well? \$\endgroup\$ – nhgrif Aug 6 '14 at 22:20
  • 1
    \$\begingroup\$ @nhgrif I think that that would be a good move. There is little benefit to distinguishing between Python 2.6 and 2.7. \$\endgroup\$ – 200_success Aug 6 '14 at 22:22
  • 1
    \$\begingroup\$ @nhgrif I also agree with that. There aren't many situations where you can't install the latest subversion without introducing breaking changes. If needed, the users can still specify the exact subversion needed for their code, but it would be better to have python-2.x and python-3.x. While the .x part is not essential, it helps to make it explicit that all the subversions are taken into account. \$\endgroup\$ – Morwenn Aug 7 '14 at 8:51

You must log in to answer this question.

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