3.5.0 release

Release notes mention 3.5.0 and also compliant versioning. When can we expect to see that on pypi?

@Łukasz Langa this bit me recently when one of my dependent modules installed future. Will you be uploading 3.5.0 to PIP?

Yes, I'm working on it.

Any progress on this? I'm trying to use the from backports import configparser syntax to avoid the conflict with python-future, but that's not present in 3.3.0r2, which is the latest release that pip gets automatically.

I've gone through the open issues: two (#9, #10) appear to not really be problems, and the other three (#8, #11, #12) would be fixed by a new (non-pre) release.

I may just reupload 3.5.0b2 under a different name, but I'd rather not! ;-)

I'm sorry, I got derailed on this. It should be out tomorrow, I'm merging some fixes that went through in the mean time.

Thanks Łukasz!

Ping? ;-)

OK, I'll upload it to PyPI under a different name tomorrow if nothing happens in the meantime.

No need for that. I'll just re-upload without the "b". Give me a few hours, it's midnight when I'm typing this.

Sorry for keeping you waiting for such a trivial thing. Maybe you'd like to share the ownership of the package?

Thanks Łukasz, and sorry to nag you about it. I'm happy to co-own the package, though I hope it will need very minimal ongoing maintenance.

3.5.0 is uploaded to PyPI and includes all changes up to Python 3.5.1. Everybody, sorry again for being such an ass about making it happen. Those backports are tedious to work with and I've been admittedly procrastinating on this one.

Thomas, thanks for being so persistent here, it was helpful. Find me during PyCon US if you're coming, I owe you one! Also, give me your PyPI credentials so I can add you as a co-owner of this.

Thanks! I'll go and update my code that uses it.

Unfortunately I won't be at PyCon US this year - I really enjoyed it last year, but now I'm back in the UK, and Portland is a very long way away. My PyPI username is takowl; thanks again. :-)