Sfoglia il codice sorgente

gunittest docs: fix broken links (#934)

* fix Python 3 syntax error, contributed by @petrasovaa
* fix broken links
Markus Neteler 4 anni fa
parent
commit
a910a52363
2 ha cambiato i file con 6 aggiunte e 6 eliminazioni
  1. 1 1
      lib/python/docs/conf.py
  2. 5 5
      lib/python/docs/src/gunittest_testing.rst

+ 1 - 1
lib/python/docs/conf.py

@@ -46,7 +46,7 @@ grass_version = core.version()['version']
 today = date.today()
 today = date.today()
 
 
 copy("_templates/layout.html.template", "_templates/layout.html")
 copy("_templates/layout.html.template", "_templates/layout.html")
-with open("_templates/layout.html", "a+b") as f:
+with open("_templates/layout.html", "a") as f:
     f.write(footer_tmpl.substitute(grass_version=grass_version, year=today.year))
     f.write(footer_tmpl.substitute(grass_version=grass_version, year=today.year))
     f.close()
     f.close()
 
 

+ 5 - 5
lib/python/docs/src/gunittest_testing.rst

@@ -668,9 +668,9 @@ Analyzing quality of source code
 Besides testing, you can also use some tools to check the quality of your code
 Besides testing, you can also use some tools to check the quality of your code
 according to various standards and occurrence of certain code patterns.
 according to various standards and occurrence of certain code patterns.
 
 
-For C/C++ code use third party solution `Coverity Scan`_ where GRASS GIS
-is registered as project number `1038`_. Also you can use `Cppcheck`_
-which will show a lot of errors which compilers do not check.
+For C/C++ code we additionally use the third party solution `Coverity Scan`_
+where GRASS GIS is registered as project number `1038`_. Also you can use
+`Cppcheck`_ which will show a lot of errors which compilers do not check.
 In any case, set your compiler to high error and warning levels,
 In any case, set your compiler to high error and warning levels,
 check them and fix them in your code. Furthermore, `Travis-CI`_ is used
 check them and fix them in your code. Furthermore, `Travis-CI`_ is used
 to check if the source code can still be compiled after submitting changes
 to check if the source code can still be compiled after submitting changes
@@ -718,8 +718,8 @@ Further reading
 .. _unittest: https://docs.python.org/2/library/unittest.html
 .. _unittest: https://docs.python.org/2/library/unittest.html
 .. _doctest: https://docs.python.org/2/library/doctest.html
 .. _doctest: https://docs.python.org/2/library/doctest.html
 .. _Coverity Scan: https://scan.coverity.com/
 .. _Coverity Scan: https://scan.coverity.com/
-.. _Travis-CI: https://travis-ci.org/GRASS-GIS/grass-ci
+.. _Travis-CI: https://travis-ci.org/github/OSGeo/grass
 .. _1038: https://scan.coverity.com/projects/1038
 .. _1038: https://scan.coverity.com/projects/1038
 .. _Cppcheck: http://cppcheck.sourceforge.net/
 .. _Cppcheck: http://cppcheck.sourceforge.net/
 .. _sandbox: https://svn.osgeo.org/grass/sandbox/wenzeslaus/grass_py_static_check.py
 .. _sandbox: https://svn.osgeo.org/grass/sandbox/wenzeslaus/grass_py_static_check.py
-.. _GRASS GIS sample data: https://grass.osgeo.org/download/sample-data and http://fatra.cnr.ncsu.edu/data/ (nc_spm_full_v2alpha)
+.. _GRASS GIS sample data: https://grass.osgeo.org/download/data/ and http://fatra.cnr.ncsu.edu/data/ (nc_spm_full_v2alpha)