FGPythonSys: Difference between revisions

Jump to navigation Jump to search
m
→‎Getting involved: http://forum.flightgear.org/viewtopic.php?f=6&t=28378&p=276624#p276624
m (→‎Getting involved: http://forum.flightgear.org/viewtopic.php?f=6&t=28378&p=276624#p276624)
Line 53: Line 53:


== Getting involved ==
== Getting involved ==
On Linux, you will want to make sure that the python3-dev package is installed (e.g. <code>sudo apt-get install python3-dev</code>, you can then set up remote tracking branches for the sg/fg and fgdata repositories, e.g.:
On Linux, you will want to make sure that the python3-dev and cppunit packages are installed (e.g. <code>sudo apt-get install python3-dev cppunit</code>, you can then set up remote tracking branches for the sg/fg and fgdata repositories, e.g.:


<pre>
<pre>
Line 62: Line 62:


{{FGCquote
{{FGCquote
|1= The code is in the branches:
|1= Just a quick update on the FGPythonSys experiment, I have push some new branches based on 2016.2.0:
* [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/flightgear/ci/python/r6/~/tree/ u-edauvergne-flightgear python/r6 branch]
* [https://sourceforge.net/u/edauvergne/simgear/ci/python/r2/~/tree/ https://sourceforge.net/u/edauvergne/simgear/ci/python/r2/~/tree/]
 
* https://sourceforge.net/u/edauvergne/fgdata/ci/python/r1/~/tree/
[https://sourceforge.net/u/edauvergne/simgear/ci/python/r4/~/tree/ u-edauvergne-simgear python/r4 branch]
 
[https://sourceforge.net/u/edauvergne/fgdata/ci/python/r2/~/tree/ u-edauvergne-fgdata python/r2 branch]
I have shifted everything around so that these branches are based on my test suite branches ([https://sourceforge.net/u/edauvergne/flightgear/ci/cppunit/r4/~/tree/ u-edauvergne-flightgear cppunit/r4] and [https://sourceforge.net/u/edauvergne/simgear/ci/cppunit/r3/~/tree/ u-edauvergne-simgear cppunit/r3]).  This means that if you install the dependency-free [https://wiki.freedesktop.org/www/Software/cppunit/ CppUnit] package and run "make test_suite", you will see 100% of FGPythonSys tested.  This is via 242 passing tests, and one deliberately failing yet temporary test.  I recommend that any Python developments based off my branches take full advantage of this infrastructure - creating tests for this infrastructure is very easy - and that the test suite remains at a 100% pass rate.
 
 
|2= {{cite web
|2= {{cite web
   | url    = http://forum.flightgear.org/viewtopic.php?p=273758#p273758
   | url    = http://forum.flightgear.org/viewtopic.php?p=276624#p276624
   | title  = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki>
   | title  = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki>
   | author = <nowiki>bugman</nowiki>
   | author = <nowiki>bugman</nowiki>
   | date  = Jan 22nd, 2016
   | date  = Feb 19th, 2016
   | added  = Jan 22nd, 2016
   | added  = Feb 19th, 2016
   | script_version = 0.23
   | script_version = 0.25
   }}
   }}
}}
}}

Navigation menu