Distribute on PyPI

[coddingtonbear]

Hey there guys!

It looks like you've properly set up your setup.py, but it doesn't look like the package is being distributed on PyPI so people (like myself) can add it as a requirement of other libraries and packages that might interface with VersionOne; this unfortunately prevents people like me from publicly releasing code that leverages your API.

Luckily -- it's super easy (seriously -- like 0 story points after you've decided whose account to use for uploading it to PyPI). I'm not sure how familiar you are with this kind of thing, so please forgive me if this reads as pedantic, but you can distribute your package (under the name you've set -- v1pysdk), by first registering your package --

python setup.py sdist register

Then, uploading the package --

python setup.py sdist upload

For future major/minor version bumps, you need only run the latter command, and it'll upload an updated package for you under your new version number.

This allows people to add your package as a requirement by adding a line to their requirements.txt or setup.py's install_requires key by adding a line reading something like v1pysdk==0.4.

Cheers!

[Atihinen]

Any comments regarding this one? I would also like this to be available on PyPI

[mtalexan]

The project hasn't been maintained. I've forked the project, fixed some bugs, and invited some commenters from this project to be Maintainers/Collaborators.
https://github.com/mtalexan/VersionOne.SDK.Python

A version is available currently under the name v1pysdk-unofficial, but it only works on Python2

[coddingtonbear]

Thanks for the invitation, @mtalexan! I'm afraid I don't happen to use VersionOne anymore, so I'm not the best candidate for helping out with maintenance. I do seem to be the person responsible for v1pysdk-unofficial, though, and I'd be glad to transfer that to you if you let me know what your PyPI username is.

Cheers, and good luck with your fork!