Suggestion: Merge `python` and `python-api` tags

Question

I would recommend that the python and python-api tags be merged.

Rationale:

• ⇒ The only part of Python that should be discussed on Blender.SE is the Blender Python (bpy) API. Anything else is not in the scope of Blender.SE and should be asked on StackOverflow.
• ⇐ Clearly anything related to the Python API is related to Python.

I have already submitted a synonym request at the python-api tag but I don't have enough rep to suggest it on the python tag. If possible it should probably be that python is kept while python-api is removed, because the latter is unnecessarily verbose.

Answer 1

Update

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

---

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 python but aren't directly related to python-api. I agree that tagging every scripting and python-api related question with python 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.

• Interactive Python workflow for Blender beginner
• How to make Blender use Python2.x?
• How to interface with blender using IPython from terminal?
• Environment for implementing/testing Computer Graphics algorithms
• Can I run a Python script step by step in Blender?
• Is there a way to acces external .blend file's data with python script?
• How to make Blender use Python2.x?
• Console vs scripting python constants
• Using blender as a python module
• Which modules are guaranteed to be present in Blender's Python?

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

Related:

• Should 'scripting' and 'Python' be made tag synonyms?
• Python tags and versions