VersionOne modified their API and test server

[mtalexan]

VersionOne recently (sometime before 2019-12-21) modified their API enough that some types of authentication no longer work. Most of the previously functional tests suddenly fail.

[fahrenberger]

The issue we are facing (oauth token authenticated servers need a different base URL now) is actually already fixed in this repository, with the addition of the use_auth_path parameter. But there is no new build on PyPi yet. I know you are not maintaining the package anymore, but it would actually be enough for many people if you just uploaded a new build with version 0.6.3 to PyPi. Right now, we are basically using the Github ZIP file to build ourselves, and everything works fine.

But it's still marked as version 0.6.2, so it can introduce clashes and missing re-build. So another option would be to simply bump the version number in your repository. That's not ideal, but with your tests failing, it might be an option? I'm not even creating a pull request for this one, since bumping the version number is just a one-liner...

[mtalexan]

If you want me to pass the PyPi ownership to you, I'm more than happy to, the prior owner passed it to me back in 2018 after it had been unmaintained for 3 years.

---

Releasing a new version on PyPi isn't quite as easy as just updating the version number since this repo doesn't have automatic build and release Actions setup. It requires building it, signing it, and then uploading it manually. I don't have any of the tools readily available to do any of that anymore, and the structure of this repo is so dated it doesn't make it easy to set it up.

If you have a working build already, I'm more than happy to grant you sole PyPi ownership and you can build, sign, and upload the wheels. Just please list yourself as owner instead of me.
If you have a public fork you can also make that the homepage.

[fahrenberger]

Sorry for the late reply. I did actually talk through this with my team. The issue is that (as of now), I cannot work on this on company time, and I don't really run any VersionOne instance in my private life. :-) Which I think is the problem with this for many possible maintainers... The final straw was that the days of VersionOne usage in our company might be numbered as well, and getting into this too deeply might not be defendable internally.

So, thanks a lot for the offer, and we totally understand and feel for your position. But since getting this running (and particularly testing) smoothly again is just not something I can get into right now.