hiccup building window wheels about btrees HOT 13 CLOSED

Actually zope.interface seems to have same problem. Maybe we don't have the right password?

https://ci.appveyor.com/project/mgedmin/zope-interface/build/1.0.95/job/tcd2ftodmdgxxo1e

from btrees.

And persistent https://ci.appveyor.com/project/mgedmin/persistent/build/1.0.32/job/0vcfg3tig0wqwkcj

from btrees.

There was that Travis password leak, after which we changed the PyPI password for zope.wheelbuilder, but then I dropped the ball and didn't change any of the Appveyor files.

I don't remember how you go about encrypting env vars for Appveyor.

This ought to be documented somewhere. sigh

from btrees.

Ok, the procedure is

• go to https://ci.appveyor.com/tools/encrypt
• paste the zope.wheelbuilder PyPI password into the text box
• hit Encrypt
• copy the encrypted value (UcdTh6W78cRLVGfKRFoa5A== into all the appveyor.ymls)

Now, is it possible somehow to retroactively build old tags but tell Appveyor to use the new encrypted value?

from btrees.

I'm going to change the appveyor.ymls to always build wheels, so that people could upload them manually in the future if something like this happens again.

I would very much like to know how to ask twine not to hang for an hour if the password is wrong.

from btrees.

I would very much like to know how to ask twine not to hang for an hour if the password is wrong.

Filed pypa/twine#224.

from btrees.

Hmm. I dropped the ball, but Tres did update the password in appveyor.yml: 585ec7e.

What went wrong?

from btrees.

By a lucky coincidence BTrees had no commits since the last tag (not even the usual post-commit version bump), so I can upload the wheels produced by this Appveyor run to PyPI manually.

The other affected packages (persistent, zope.interface, zope.index) have other commits, so no wheels until somebody makes a new release.

from btrees.

BTrees 4.4.0 wheels uploaded to PyPI.

Also, I just came up with a scheme to upload missing persistent/zope.interface/zope.index wheels:

• create a temporary branch based on the tag
• modify the credentials in appveyor.yml
• make the 'twine upload' unconditional
• better yet, change the check to upload iff setup.py --version does not contain dev
• commit and push
• wait for appveyor to build and upload
• remove the temporary branch

from btrees.

Ok, I'm attempting that thing for zope.interface: https://ci.appveyor.com/project/mgedmin/zope-interface/build/1.0.105

The builds should run in about an hour (Appveyor's free tier is slow! maybe ZopeFoundation would like to shell out for a paid account?).

from btrees.

I've queued a build for persistent too: https://ci.appveyor.com/project/mgedmin/persistent/build/1.0.63

I've no plans to build zope.index wheels, but I can, if somebody asks (preferably after they fix zopefoundation/zope.index#9).

from btrees.

zope.interface wheels have been built and uploaded to PyPI successfully.

persistent wheels for 32-bit Python have been built and uploaded to PyPI successfully. Wheels for 64-bit Python are missing because of test failures (what were fixed in master after the last release).

from btrees.

My goodness! thank you so much @mgedmin !

from btrees.