Talk:Python Minefield Breaching System
 | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||
| |||||||||||||||||||||||
.svg)
Trailer weight
[edit]given that the trailer is towed by a freaking tank in the picture and still looks quite large, and the fact that the weight of the explosives is stated as one and a half ton, how can it still weigh only 136 kilograms?
MikeTango (talk) 17:24, 21 January 2012 (UTC)
Requested move 18 October 2024
[edit]
 | It has been proposed in this section that Python Minefield Breaching System be renamed and moved to Python minefield breaching system. A bot will list this discussion on the requested moves current discussions subpage within an hour of this tag being placed. The discussion may be closed 7 days after being opened, if consensus has been reached (see the closing instructions). Please base arguments on article title policy, and keep discussion succinct and civil. Please use {{subst:requested move}}. Do not use {{requested move/dated}} directly. |
Python Minefield Breaching System → Python minefield breaching system – Not a proper name. Appears this way in a headline, but also appears lowercase in the article. Also called Python minefield clearing system, Python mine-clearing system in the cited sources. Dicklyon (talk) 19:42, 18 October 2024 (UTC)
- Support, lowercase the description of equipment type per precedents listed in User:Dicklyon/MIL precedents. It's a replacement for the Giant Viper, and would simply be called the Python if not for the need to distinguish it from biology (and computing) articles. — BarrelProof (talk) 21:20, 18 October 2024 (UTC)