Once #142 will have been merged, can you rebase your branch on master ? then it should pass the tests.
Thx.

👍

Don't bother rebasing. I can merge anyways.

Thank you for contributing!

Twine kind of broke a release. I tried uploading 1.0.1 and and it didn't let me enter my gpg passphrase. It ended up uploading a bad signature and I had to bump the version to 1.0.2. I'm on twine v1.3.1, I'll try again with the latest version next time.

Really? :( /cc @dstufft

That's odd... All twine is doing is subprocess to gpg. and failing to sign should get a non zero exit code and stop the upload.

You can test things on testpypi.python.org before sending to pypi.python.org for what it's worth. Also twine lets you pre-sign files too. Just specify the .asc files on the CLI invocation too like:

$ twine upload foo-1.0.tar.gz foo-1.0.tar.gz.asc

This is my log

reazem@cranberry:~/git/influxdb-python$ twine upload --sign dist/*
Uploading distributions to https://pypi.python.org/pypi
Signing influxdb-1.0.0-py2.7.egg

You need a passphrase to unlock the secret key for
user: "Alexandre Viau alexandre@alexandreviau.net"
4096-bit RSA key, ID 3CCC3A3A, created 2014-04-01

Uploading influxdb-1.0.0-py2.7.egg
Signing influxdb-1.0.1-py2.py3-none-any.whl

You need a passphrase to unlock the secret key for
user: "Alexandre Viau alexandre@alexandreviau.net"
4096-bit RSA key, ID 3CCC3A3A, created 2014-04-01

Uploading influxdb-1.0.1-py2.py3-none-any.whl

It didn't prompt you for the passphrase at all, or when it did it didn't let you type it in?

It didn't prompt me for the password. When I saw that the 3 files still got uploaded I canceled with CTRL-C. Maybe I should have waited for the command to complete?

Then I tried to upload again and pypi told me the files were already there.