Python in FlightGear: Difference between revisions

Jump to navigation Jump to search
Line 72: Line 72:


== Status ==
== Status ==
RFC (forum debate)
{{FGCquote
|1= In summary, I have implemented the FGPythonSys subsystem to provide access to the embedded Python interpreter and have implemented the 'props' data structure for accessing the property tree.  The code is in the branches:
    [https://sourceforge.net/u/edauvergne/flightgear/ci/python/r3/~/tree/ https://sourceforge.net/u/edauvergne/flightgear/ci/python/r3/~/tree/]
 
    [https://sourceforge.net/u/edauvergne/simgear/ci/python/r2/~/tree/ https://sourceforge.net/u/edauvergne/simgear/ci/python/r2/~/tree/]
|2= {{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=273758#p273758
  | title  = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki>
  | author = <nowiki>bugman</nowiki>
  | date  = Jan 22nd, 2016
  | added  = Jan 22nd, 2016
  | script_version = 0.23
  }}
}}
 
{{FGCquote
|1= After some long forum discussions [1], followed by some private discussions with Curt about his own Python property system developments, I have written some code that might be of general interest. This started as an experiment to learn more about the design of the complicated Python object data structure, but it has expanded somewhat. The code is currently for experimentation, as only the property tree is accessible. It is written to be compatible only with Python 3k, as py2 support is not needed for an interpreter compiled into the fgfs binary.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34787850/
  | title  = <nowiki>[Flightgear-devel] A FGPythonSys implementation: The embedded
Python interpreter as a FlightGear subsystem.</nowiki>
  | author = <nowiki>Edward d'Auvergne</nowiki>
  | date  = Jan 22nd, 2016
  | added  = Jan 22nd, 2016
  | script_version = 0.23
  }}
}}


== Roadmap ==
== Roadmap ==

Navigation menu