Merging development upgrades into master + PyPI release

[dineshpinto]

Hey Olivier,

There are some major changes in this upgrade:

• Full project refactoring, the project style was a bit confusing, so I've refactored it to be PEP8 compliant.
• Switch build stack to Poetry with a pyproject.toml file, its a lot more modern, and makes it easier to handle dependencies and publish projects compared to setup.py
• Bump version to v0.3.0, since this would be a bigger change

Minor changes:

• Bugfix for Issue #32
• Switched string comparison operators to == instead of is, which is known to cause some weird edge cases
• Fixed import bugs where the incorrect function was called
• Placed some TODOs in the code, where function parameters were undefined

All tests pass successfully.

I would like to integrate pySPM as a first class dependency in one of my own projects (qudi-hira-analysis). Unfortunately, the current PyPI version of pySPM doesn't have the latest bugfixes needed by my project. And PyPI requires all the dependencies to be on PyPI too.

Therefore, I would like to create a new PyPI release for the latest version of pySPM. I have set the version to 0.3.0, so that (if there are any bugs not picked up by the testing) existing users on v0.2.x will not be affected. I know you are not actively maintaining this library anymore, so I would be happy to do that if you wish.

Let me know what you think.

Cheers, Dinesh

[scholi]

Thank you very much for your contribution. Great job!

[scholi]

Do you have a pypi account? I can add you and you can thus also create new packages. Ah yes. I found you

[dineshpinto]

Perfect, thanks