This is the talk page for discussing improvements to the Python (missile) article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This page is not a forum for general discussion about Python (missile). Any such comments may be removed or refactored. Please limit discussion to improvement of this article. You may wish to ask factual questions about Python (missile) at the Reference desk. |
This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||||
|
The contents of the Shafrir page were merged into Python (missile) on March 2012. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. |
Operators
editI read somewhere that the South African Air Force (SAAF) acquired a small number of Python 3 and possibly Derby missiles for use with the Atlas/Denel Cheetah and Mirage F-1 models in the mid-1980s. This measure was presumably taken in response to the deployment of MiG-23ML/MF aircraft with AA-7 and AA-8 missiles in Angola, which were capable of all-aspect target acquisition, whereas the SAAF's Matra 550 and V-3 Kukri missiles were only capable of tail-hemisphere attacks on adversary aircraft--a severe handicap, which the Python's all-aspect capability solved to some degree. Can anyone verify whether or when the SAAF acquired the Python 3? —Preceding unsigned comment added by 206.111.29.1 (talk) 23:12, 5 January 2011 (UTC)
DeepSpace's recent edit
editThe recent edit[1] by User:DeepSpace reads (to me at least) like advertising copy; I think it has NPOV problems, for example consider this except:
- The Python 5's head seeker literally sees a clear image of the target and background, giving it an incredible advantage over other missiles by authenticating the target, thus reducing the chance of being mislead by counter measures. Using this technology allows the luxury of locking on a target after the launch. The transition to this unique technology required a development by RAFAEL, which exists in only several countries in the world.
(I've emphasized some of the words which I think may be a breach of the NPOV policy. I would also note that something can hardly be "unique" if it "exists in several countries in the world")
User:DeepSpace has only made two edits, the other one of which was vandalism.
Should this edit just be reverted?
-- Cabalamat 19:32, 19 Dec 2004 (UTC)
Maybe just clean it up a little bit. It did bring a lot more info on this subject, so rv-ing it might not be the best.
--Borisborf
- Just found that he copied word-for-word out of this website which is not public-domain:
http://www.israeli-weapons.com/weapons/missile_systems/air_missiles/python/Python5.html This must be RVed.
I cleaned up the page and added variuos Python-family missile info. -- Adeptitus 19:54, 30 June 2006 (UTC)
there should be seperate article for derby
editi thought python-3/4 and 5 are different from each other. And derby is a medium range missile. shouldn't we have seperate article for each missile
True, but this is a general Python Missile page with consolidated info. -- Adeptitus 18:04, 5 July 2006 (UTC)
Python-Shafrir merge idea
editI completly disagree with the idea of merging these two articles. The two missile series really share nothing save the fact that they both originated in Israel. The Shafrir 1 was virtually a unlicensed copy of the early-model Sidewinders. The Pythons did grow upon the experience the Israelis had with not only the Shafrir, but also the Sidewinder and other missile series, however, they are a completly independent development from anything else in the world. There is no doubt that both articles need a fair amount of work done to them (they are quite insufficient in several respects and need work). They Pythons and Shafrirs deserve their own articles. An equivalent would be placing the Sparrow and the AIM-120 Slammer in the same article because the latter grew from the former. There is my reasoning. I have noticed that the member who suggested the merger has not expressed his motivations yet. I urge you to do this. —Preceding unsigned comment added by SAWGunner89 (talk • contribs) 02:59, 10 July 2008 (UTC)
Shafrir and Python articles should be either merged or completely separated. There is no reason to list the Shafrir missiles under "Versions" section here, and the same text in Shafrir article. Flayer (talk) 17:39, 16 September 2010 (UTC)
Please do not duplicate discussions, see Talk:Shafrir --Jor70 (talk) 20:38, 17 September 2010 (UTC)
Inconsistensies
editThe 35 kills during the lebanon war is contradicts the sidewinder article where 51 of 55 kills where with Sidewinders. Also the Pythin 4 is described as having limited Fire and Forget capability??? All IR missiles have full fire and forget capability because of the IR guidance not relying on the launch aircraft after launch. I suspect it's been misstaken for "lock after launch" as a helmet mounted sight is mentioned in conjunction with it. —Preceding unsigned comment added by 85.228.57.204 (talk) 01:59, 27 April 2011 (UTC)
RAFAEL Python
editRAFAEL - Armament Development Authority (Hebrew: רפא"ל - רשות לפיתוח אמצעי לחימה) changed its name to
Rafael - Advanced Defense Systems Ltd. (Hebrew: רפאל - מערכות לחימה מתקדמות בע"מ). It was an acronym, now it is not. Therfore instead of RAFAEL Python it should be Rafael Python. Flayer (talk) 23:46, 20 March 2012 (UTC)
BVR undefined
editDoes BVR mean "Beyond Visual Range"? — Preceding unsigned comment added by 50.43.11.252 (talk) 03:23, 15 July 2014 (UTC)
- Yes. See Beyond-visual-range missile. I will turn the acronym "BVR" into a blue link and this will eliminate the obvious problem in the article. Thanks for drawing it to our attention. Dolphin (t) 06:40, 20 July 2014 (UTC)