20,741
edits
FGPythonSys: Difference between revisions
Jump to navigation
Jump to search
→Dependencies
| Line 179: | Line 179: | ||
== Concerns and Issues == | == Concerns and Issues == | ||
=== Dependencies === | === Dependencies === | ||
{{FGCquote | |||
|1= Many posters were chiefly enthusiastic about Python because of the many libraries that can be used. However, I'd much like to avoid a situation like 'If you fly this plane, you in addition have to install Python libs X and Y, if you fly that plane it requires lib Z - oh, and that custom scenery uses lib Q for animation of jetways,...' - I trust you see the picture. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34789043/ | |||
| title = <nowiki>Re: [Flightgear-devel] A FGPythonSys implementation: The embedded | |||
Python interpreter as a FlightGear subsystem.</nowiki> | |||
| author = <nowiki>Thorsten Renk</nowiki> | |||
| date = Jan 23rd, 2016 | |||
| added = Jan 23rd, 2016 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote | ||
|1= Like Thorsten I'm not keen in this. It would be a nice addition only if it was never used anywhere within the distribution. (FlightGear itself, FGData, FGAddon). I see some value in it for side projects but not for end users. | |1= Like Thorsten I'm not keen in this. It would be a nice addition only if it was never used anywhere within the distribution. (FlightGear itself, FGData, FGAddon). I see some value in it for side projects but not for end users. | ||