Move python api code to own file

[RonnyPfannschmidt]

Thanks for submitting a PR, your contribution is really appreciated!

Here's a quick checklist that should be present in PRs:

• Add a new news fragment into the changelog folder
  • name it $issue_id.$type for example (588.bug)
  • if you don't have an issue_id change it to the pr id after creating the pr
  • ensure type is one of removal, feature, bugfix, vendor, doc or trivial
  • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."
• Target: for bugfix, vendor, doc or trivial fixes, target master; for removals or features target features;
• Make sure to include reasonable tests for your change if necessary

[nicoddemus]

Perhaps we should call the new file just api.py?

[nicoddemus]

Also what's the intent for moving those classes?

[RonnyPfannschmidt]

@nicoddemus cutting down the file sizes before introducing FunctionDefinition?

[nicoddemus]

OK, was just wondering. python_api sounds like something we want to make public, that's why I asked.

[RonnyPfannschmidt]

wrt the filename - api.py seems a bit short and non-saying - same for python api

i do wonder about splitting logical bits into more files

[coveralls]

Coverage increased (+0.004%) to 92.132% when pulling cce9c99 on RonnyPfannschmidt:move-python-api into 467c526 on pytest-dev:features.

[RonnyPfannschmidt]

but yeah, this can be merged ^^

[coveralls]

Coverage increased (+0.004%) to 92.132% when pulling f8b2277 on RonnyPfannschmidt:move-python-api into 467c526 on pytest-dev:features.