Skip to main content
Commonmark migration
Source Link

##Update

Update

The tag was removed since people ignore the subtle differences, it's now just .


I am tempted to merge these ever so often but since we support a strict subset of Python related questions, it is ok to have both of these in my opinion.

There are currently questions here that use but aren't directly related to . I agree that tagging every and related question with is kinda redundant and the last two seem to be used interchangeably but at the moment, the tag is general enough to also apply to these.

Here are some tagged Python questions that have little or nothing to do with the api.

What we could do however is revisit the scope of this tag.

Related:

##Update

The tag was removed since people ignore the subtle differences, it's now just .


I am tempted to merge these ever so often but since we support a strict subset of Python related questions, it is ok to have both of these in my opinion.

There are currently questions here that use but aren't directly related to . I agree that tagging every and related question with is kinda redundant and the last two seem to be used interchangeably but at the moment, the tag is general enough to also apply to these.

Here are some tagged Python questions that have little or nothing to do with the api.

What we could do however is revisit the scope of this tag.

Related:

Update

The tag was removed since people ignore the subtle differences, it's now just .


I am tempted to merge these ever so often but since we support a strict subset of Python related questions, it is ok to have both of these in my opinion.

There are currently questions here that use but aren't directly related to . I agree that tagging every and related question with is kinda redundant and the last two seem to be used interchangeably but at the moment, the tag is general enough to also apply to these.

Here are some tagged Python questions that have little or nothing to do with the api.

What we could do however is revisit the scope of this tag.

Related:

replaced http://blender.stackexchange.com/ with https://blender.stackexchange.com/
Source Link

##Update

The tag was removed since people ignore the subtle differences, it's now just .


I am tempted to merge these ever so often but since we support a strict subset of Python related questions, it is ok to have both of these in my opinion.

There are currently questions here that use but aren't directly related to . I agree that tagging every and related question with is kinda redundant and the last two seem to be used interchangeably but at the moment, the tag is general enough to also apply to these.

Here are some tagged Python questions that have little or nothing to do with the api.

What we could do however is revisit the scope of this tag.

Related:

##Update

The tag was removed since people ignore the subtle differences, it's now just .


I am tempted to merge these ever so often but since we support a strict subset of Python related questions, it is ok to have both of these in my opinion.

There are currently questions here that use but aren't directly related to . I agree that tagging every and related question with is kinda redundant and the last two seem to be used interchangeably but at the moment, the tag is general enough to also apply to these.

Here are some tagged Python questions that have little or nothing to do with the api.

What we could do however is revisit the scope of this tag.

Related:

##Update

The tag was removed since people ignore the subtle differences, it's now just .


I am tempted to merge these ever so often but since we support a strict subset of Python related questions, it is ok to have both of these in my opinion.

There are currently questions here that use but aren't directly related to . I agree that tagging every and related question with is kinda redundant and the last two seem to be used interchangeably but at the moment, the tag is general enough to also apply to these.

Here are some tagged Python questions that have little or nothing to do with the api.

What we could do however is revisit the scope of this tag.

Related:

replaced http://meta.blender.stackexchange.com/ with https://blender.meta.stackexchange.com/
Source Link

##Update

The tag was removed since people ignore the subtle differences, it's now just .


I am tempted to merge these ever so often but since we support a strict subset of Python related questions, it is ok to have both of these in my opinion.

There are currently questions here that use but aren't directly related to . I agree that tagging every and related question with is kinda redundant and the last two seem to be used interchangeably but at the moment, the tag is general enough to also apply to these.

Here are some tagged Python questions that have little or nothing to do with the api.

What we could do however is revisit the scope of this tag.

Related:

##Update

The tag was removed since people ignore the subtle differences, it's now just .


I am tempted to merge these ever so often but since we support a strict subset of Python related questions, it is ok to have both of these in my opinion.

There are currently questions here that use but aren't directly related to . I agree that tagging every and related question with is kinda redundant and the last two seem to be used interchangeably but at the moment, the tag is general enough to also apply to these.

Here are some tagged Python questions that have little or nothing to do with the api.

What we could do however is revisit the scope of this tag.

Related:

##Update

The tag was removed since people ignore the subtle differences, it's now just .


I am tempted to merge these ever so often but since we support a strict subset of Python related questions, it is ok to have both of these in my opinion.

There are currently questions here that use but aren't directly related to . I agree that tagging every and related question with is kinda redundant and the last two seem to be used interchangeably but at the moment, the tag is general enough to also apply to these.

Here are some tagged Python questions that have little or nothing to do with the api.

What we could do however is revisit the scope of this tag.

Related:

added 131 characters in body
Source Link
iKlsR
  • 43.6k
  • 1
  • 23
  • 56
Loading
Source Link
iKlsR
  • 43.6k
  • 1
  • 23
  • 56
Loading