20,741
edits
Python in FlightGear: Difference between revisions
Jump to navigation
Jump to search
→Background
| Line 54: | Line 54: | ||
| date = Dec 28th, 2015 | | date = Dec 28th, 2015 | ||
| added = Dec 28th, 2015 | | added = Dec 28th, 2015 | ||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= there are no promises ahead of time that we will roll python integration into the core source code ... especially before seeing actual code and seeing how the integration looks, understanding what parts of the code and build system need to be touched, making sure it can be supported on all platforms, and pondering some of the bigger issues brought up in this thread. But there are a lot of python fans floating around the FlightGear community so I think you could build up some interest, especially if you were able to get some early prototype integration working and show some examples. Maybe in the process you'll stumble on a really compelling or creative use for python that nasal can't match? Maybe in the process you'll stumble on some show stopper problem and we'll learn some lessons. We do have some precident for including optionally compiled features in FlightGear, so if you can come up with a clean integration, but larger objections remain, perhaps we can make it an optionally compiled feature so those with interest can pursue it, and those with concerns can avoid it ... at least for the near term. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=270580#p270580 | |||
| title = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki> | |||
| author = <nowiki>curt</nowiki> | |||
| date = Dec 29th, 2015 | |||
| added = Dec 29th, 2015 | |||
| script_version = 0.23 | | script_version = 0.23 | ||
}} | }} | ||