Updated Latvian translation
Release 1.6.0
Post release version bump
Better SIGINT handling for python signals module

Even though PyInitialize_Ex does not initialize signal handlers,
the python signal module does install a handler for SIGINT when
the handler for SIGINT is set to SIG_DFL on importing the signal
module.

To avoid applications not handling SIGINT we set a custom SIGINT
handler (if the current SIGINT handler is SIG_DFL) before
initializing the python interpreter. This signal handler when
invoked simply chains to the default SIGINT handler.

https://bugzilla.gnome.org/show_bug.cgi?id=682014
Added kn.po, updated Kannada translation and added kn to LINGUAS file
Release 1.6.1
Post release bump version
Added slovak translation
Workaround gjs single-include issue

gjs features single-include guards for the headers in gjs/ with
gjs/gjs-module.h being the only header you are supposed to include.

Unfortunately, the headers in gi/ (which do not appear to have their own
master include file) individually include files from gjs/.

We can workaround the issue by first #include <gjs/gjs-module.h> which
will skip the single-include guard on the files the second time they get
included (from the headers in gi/).

https://bugzilla.gnome.org/show_bug.cgi?id=688617
Fix another gjs single-include issue instance

The tests have the same problem as the loader itself and the last commit
missed that.  Fix it too.

https://bugzilla.gnome.org/show_bug.cgi?id=688617
Release 1.6.2
Added Odia Language into the List.
Updated Odia Translation with FUEL implementation.
Updated Kannada Translations
Updated Friulian translation
Prevent python from generating binary files

Do not generate .pyc and __pycache__ files in the tests: they are not
needed and break distcheck
Support py2 and py3 at the same time

This patch reworks the build system so that we use the same sources to
build both a python2 loader and a python3 loader. The python 2 one
keeps the same name for backward compatibility, while the python 3 one
is explicitely called "python3".
Supporting py2 and py3 in the same build is tricky since the existing
autotools support is limited, so we make some assumptions:
 - there are separate --enable-python2 and --enable-python3 flags,
   --enable-python has been removed
 - the py3 loader is in a separate dir but compliles the files from the
   py2 loader
 - for py2 we only check the binary and the python2-config tool, while
   for py3 we use the proper AM_PATH_PYTHON macro
 - for py2 we manually detect pyexecdir, hopefully with the same logic
   used by the AM_PATH_PYTHON macro
 - we do not check for Python.h header anymore since it is not strictly
   needed and autoconf caching makes it difficult
 - for we build the demos only for python3 (unit tests instead are
   replicated for both)

https://bugzilla.gnome.org/show_bug.cgi?id=691081
Remove outdated mention of pygi from README
Release 1.7.0
Post-release version bump