Guido, The reason why I use a code name is that it would be dangerous to reveal my true name to the world since there are those who are radical liberals who would like to think that there is no need for a U.S. military and that people such as myself should be eliminated. Think of the U.S. military as the heroes that they truly are to protect its citizens from attack from other entities. The U.S. military is here to serve and protect people such as yourself, not to act as the terrorist organization as bin laden would like you to think. If any of you need any further evidence of the need of the U.S. military or the F-35 for that matter, then I would suggest that you all take a nice long trip to Manhattan island in New York City and take some time to notice the fact that there appears to be a large hole where many buildings used to be located. Second, the biggest concern that I see in utilizing the python language in safety-critical systems is that it is a dynamically type language. Unlike Ada which is safety statically type language. These were just brainstorming ideas, but if you do not like those that brainstorm regarding the further development of python, then I guess I will be moving forward to some other language that is more capable to assist in the development of safety critical systems. These were just brainstorming ideas. The idea being is to research onto the idea of developing a statically type variant of the python language for the development of software for safety critical systems. Is this possible? I am also wondering if it was possible to interface Ada programs with Python, similar to the method that has been utilized to interface FORTRAN with Python. Is this also possible? Thank You. W108dab
--- On Sat, 6/13/09, Guido van Rossum email@example.com wrote:
From: Guido van Rossum firstname.lastname@example.org Subject: Re: [Python-Dev] FINAL PROPULSION OPEN SOURCE ENGINE VARIANT FOR THE F-35 JOINT STRIKE FIGHTER To: "OMEGA RED" email@example.com Date: Saturday, June 13, 2009, 11:58 AM
I'm sorry, but I have so far three problems with your proposals.
(1) You use a code name.
(2) Your first message was ALL CAPS.
(3) You don't seem to know much about programming language design, or you wouldn't propose such a vague non-starter as "adopt the safety-critical charasteristics of the Ada programming language an incorporate them into Python."
This is my last message to you.
On Sat, Jun 13, 2009 at 7:27 AM, OMEGA REDomega_force2003@yahoo.com wrote:
I think that python developers would be great in the development of the FADEC controller as an open-source alternative to the propreitary FADEC controller software to the propulsion system for the F-35. The FADEC controller is Full Authority Flight Digital Electronic Controller.
I know that the python community could never possibly create the mechanical aspects of this proposed engine, but that does not mean that we cannot create something else.
I believe that what could be done is to create a safety-critical version of python. Such as adopt the safety-critical charasteristics of the Ada programming language an incorporate them into python.
How about that as a project? Create the python equivalent of Ada?
Subject: Re: [Python-Dev] FINAL PROPULSION OPEN SOURCE ENGINE VARIANT FOR THE F-35 JOINT STRIKE FIGHTER To: "OMEGA RED" firstname.lastname@example.org Date: Saturday, June 13, 2009, 6:16 AM
I'm reasonably confused here, are you searching for Python developers?
On Fri, Jun 12, 2009 at 7:01 PM, OMEGA RED email@example.com wrote:
I AM HAPPY TO SAY THAT I AM NOW IN THE PROCESS OF DEVELOPING A WEBSITE FOR THE STATED PURPOSE OF COMBINING SOME OF THE BEST MINDS IN THE WORLD. THIS PROJECT WILL BE A MEANS TO DEVELOP THE FIRST AND ONLY COMPLETELY OPEN SOURCE VARIANT OF THE PROPULSION ENGINE FOR THE F-35 JOINT STRIKE FIGHTER. WHICH MEANS THAT EVERYTHING ABOUT THE DESIGN, DEVELOPMENT, AND CONSTRUCTION OF THE ENGINE WILL BE COMPLETELY AVAILABLE TO THE PUBLIC AND TO ANY ENGINE MANUFACTURE FREE OF ANY REQUIREMENTS.
THIS ENGINE WILL BE CALLED THE PHOENIX NexT F-200 ENGINE.
THIS ENGINE WILL ALSO BE A POTENTIAL THIRD AND FINAL ALTERNATIVE ENGINE FOR THE JOINT STRIKE FIGHTER.
THIS ENGINE WILL BE STATED AS BEING A COMPETITOR WITH BOTH THE F-135 AND THE F-136 ENGINE, WHICH ARE PROVIDED BY BOTH PRATT-WHITNEY AND GENERAL ELECTRIC/ ROLLS ROYCE.
THIS ENGINE WILL UTILIZE PYTHON FOR THE MAJOR PORTION OF THE SIMULATION, RESEARCH AND DEVELOPMENT STAGES FOR THE DEVELOPMENT OF THE ENGINE. THE CONSTRUCTION OF THE MATHEMATICAL PROCESSING OF THE REQUIRED NONLINEAR CONTROLS WILL BE BASED ON A SPECIALIZED VERSION OF GROUP THEORY FOR THE DESIGN AND CONSTRUCTION OF THE NONLINEAR CONTROL SYSTEMS.
THE PURPOSE OF THE DEVELOPMENT OF THE ENGINE WILL BE TO CONSTRUCT AN ENGINE FOR THE F-35 THAT WILL BE AS RELIABLE AND CAPABLE AS THE F-135 AND THE F-136.
HOWEVER, THE PHOENIX NexT ENGINE WILL ALSO BE STATED AS BEING ONLY AROUND $20,000 TO $110,000 DOLLARS TO BEING PURCHASED BY AN OPERATOR OF THE F-35, WHICH WILL BE AN INSIGNIFICANT COST COMPARED TO THE COST OF BOTH THE F-135 AND THE F-136 ENGINE (10 MILLION DOLLARS PER UNIT).
HOW MANY OUT THERE WANT TO HELP IN THIS ENDEAVOR ? I BELIEVE THAT WE ALL CAN SUCCEED WHERE BOTH PRATT-WHITNEY AND GE/ROLLS ROYCE HAVE FAILED TO DEVELOP AN INEXPENSIVE AND RELIABLE ENGINE FOR THE F-35.
Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/josepharmbruster%40gmail.c...
Enough is enough guys. As entertaining as this thread has been, shouldn't we be focused on the 3.1 release?
Don't feed the trolls. Ok so one wandered in, but nobody needed to respond and it can only get worse from here.
Please just flag the offending address(es) for moderation and ask them politely to keep their posts to this list on-topic for core Python development.