20,741
edits
FGPythonSys: Difference between revisions
Jump to navigation
Jump to search
→Status
(→Status) |
|||
| Line 343: | Line 343: | ||
== Status == | == Status == | ||
{{FGCquote | |||
|1= I'm also battling with VS 2015 (msvc14) on a VirtualBox VM with Windows 7. I need to have this system up and running, because Windows support for FGPythonSys is essential. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=283183#p283183 | |||
| title = <nowiki>Re: FGPython an propose for </nowiki> | |||
| author = <nowiki>bugman</nowiki> | |||
| date = Apr 22nd, 2016 | |||
| added = Apr 22nd, 2016 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote | ||
|1= Just a quick update, now that I have a test suite up and running (I'll post full details on the devel mailing list), I'm now working on a 'fg_sys' Python module to supply 'sys' module equivalent functions. The initial aim of this basic infrastructure is to replace sys.stdout and sys.stderr so that this works through the SG_LOG() system, allowing all printouts and feedback to go through the normal FlightGear/SimGear IO channels. | |1= Just a quick update, now that I have a test suite up and running (I'll post full details on the devel mailing list), I'm now working on a 'fg_sys' Python module to supply 'sys' module equivalent functions. The initial aim of this basic infrastructure is to replace sys.stdout and sys.stderr so that this works through the SG_LOG() system, allowing all printouts and feedback to go through the normal FlightGear/SimGear IO channels. | ||