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?
I generally agree with this proposal, and it goes to show that tag curation is often somewhat inconsistent.
In particular to your question, retagging questions related to Python-based modelling packages is a very doable case. A quick advanced search brings up 51 potential questions to be retagged with the addition of python. These are potential questions because
there may already be five relevant tags on a question;
a question asking about such packages may not be intrinsically related to Python; for instance What is the purpose of libraries like Pyomo and Google OR tools? is a "meta-library" question, so take care not to robo-tag.
It is important to avoid mass retagging as it would flood the main page with questions pertaining to one topic only and would deprive new questions of attention. Advice from related sites suggests no more than five instances per day, but due to our site being smaller I would go for a maximum of three of these retagging edits per day.
On a wider note, it may be helpful to form guidelines on the limits of these encompassing tags, or whether there should be limits at all. For example, how far do we want to go with solver (as raised in the comments), constraint or optimization?