When tagging questions related to Python-based packages — such as cplex-python-api, cvxpy, pulp, pyomo — tag python is sometimes included and sometimes not. It would be nice to have a policy on this.
In my humble opinion, if there is room for an extra tag, then the "mother tag" python should always be included, though not everyone agrees. Imagine that someone who is fond of Python visits Operations Research SE for the first time. That someone can click on tag python, take a look at the related tags and find about, say, CVXPY and PuLP. If there is room for tag python, why would one want to deprive neophytes and outsiders of the opportunity to quickly learn about the tools of the trade? If the cost is zero and the payoff is nonnegative, why object to it?
python
, I found usingpython
withcvxpy
(in your example) redundant.cvxpy
orpulp
are python packages. With that argument, we can keep generalizing tags. e.g. maybe we should then start tagging allcplex
,gurobi
and such with asolver
tag as well, in hope someone can learn what are the solvers. That's my opinion but I'm curious to see what others think and hopefully, we can have some standards around it. And thanks for the question. $\endgroup$Related
column. Also, perhaps search engines will direct more people to OR SE, which should produce more good than harm. Ideally, SE would have tag hierarchies with "mother tags" and "children tags" — like Quora — and one would be able to search not only within a tag, but also within its children, but we have no such luck. $\endgroup$python
isn't redundant. I might search forpython
because it's the language I'm comfortable using, but if I've never heard ofcvxpy
I'd never think of searching for it and I'd never find that perfect answer to my problem. $\endgroup$tikz-pgf
(a LaTeX graphics package) plusedge
or some other object within thetikz-pgf
package. $\endgroup$numpy
are also tagged withpython
. I am a convert. $\endgroup$