Users cannot do anything about this as they are not using
the methods directly. If they use them they will see
the warning but we do not want to see them if we are silently
accessing them.

When opening a script with an import (including the default ones) and a syntax error it caused a crash.
This occured due to the code completion failing to parse the import
An extra check has been added to avoid the crash

Switching to BytesIO and encoding the string means that cStringIO does
not need to be used which is not present in python 3.

Scripts containing an encoding declaration in the first two lines are
now able to be run without errors or encoding artefacts.

As the declaration cannot compiled properly is not encoded and causes
encoding artefacts if other parts containing unicode characters are
encoded, the solution has been to remove the declaration from the code
to be run if there would be a failure.

Not all objects have a __module__ attribute so make
sure it is there before we attempt to access it
Refs #27337

Key words such as 'for', 'print', etc. provided by the 'keyword' module.

Given an import "import numpy as np" the call tips were previously
stored as e.g. "numpy.arange". This displayed "arange (numpy)" as a call
tip but would not display the parameters after completing on "np.ar".
We now store the completion as "np.arange" so that parameters are
displayed after the completion.

The docstring explains why we're writing our own completion class rather
than using a packaged like jedi.

Make CodeCompleter inherit from object.

Builtin functions do not have function signatures and so its not
possible to find it argument via code inspection. Generate the call tips
using the functions' docstrings instead.

Add numpy and matplotlib autocompletion tests

Add completions for the modules if they are imported in the script.

jedi's autocompletion generation can be a little slow. Add some more
conditions so that it is not run so much.

QSci has a bug where it will not display call tips in the GUI the first
time you enter a bracket for a function. You need to either enter an
argument and a comma, or delete the bracket and put it back in again.
Since jedi's completions are updated on every key movement the call tips
will never show unless they are persistent.

Re-factor 'get_function_spec' and 'generate_call_tips' out of the
CodeCompleter class and into standalone functions.

jedi crashes when launched using PyCharm's debugger on Python 2. Having
jedi as optional means we can still use the debugger whilst we're not
using Python 3.

Only add functions/builtins from simple api if they are title case and
don not begin with a '_'.

Add jedi's static code analysis completions to the CodeCompleter class.

Only generate the call tips if the simple api import is present in the
script.

Add CodeCompleter tests to CMakeLists

New CodeCompleter class contains the logic for populating QScintilla's
completion API. It's CodeCompleter.update_completion_api is called
whenever a script is successfully run.