You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of the C extensions this doesn't quite fit our standard model.
I have some github actions YAML from other repos that deal with C extensions and building/uploading Mac/Linux[32-bit, 64-bit, aarch64] wheels that I can bring over as a starting point.
Someone with access to the zope.wheelbuilder account would need to add a repository secret for TWINE_PASSWORD (a token with scoped upload rights to zope.interfacepersistent). (I could create a PyPI token from my personal account, but since we have a dedicated account I'd prefer not to.)
Environment that builds docs
32-bit linux build/upload
64-bit linux build/upload
aarch64 linux build/upload
coveralls
mac builds/upload
Pure-python tests
Compare other settings with existing "pure-python" configurations
Update badges
Update any docs references
The text was updated successfully, but these errors were encountered:
Someone with access to the zope.wheelbuilder account would need to add a repository secret for TWINE_PASSWORD (a token with scoped upload rights to zope.interface). (I could create a PyPI token from my personal account, but since we have a dedicated account I'd prefer not to.)
Heh, s/zope.interface/persistent/, but this is now done.
As with zopefoundation/zope.interface#225, since Travis CI no longer works this is probably a blocker for any other PRs.
Because of the C extensions this doesn't quite fit our standard model.
I have some github actions YAML from other repos that deal with C extensions and building/uploading Mac/Linux[32-bit, 64-bit, aarch64] wheels that I can bring over as a starting point.
Someone with access to the
zope.wheelbuilder
account would need to add a repository secret forTWINE_PASSWORD
(a token with scoped upload rights tozope.interface
persistent
). (I could create a PyPI token from my personal account, but since we have a dedicated account I'd prefer not to.)The text was updated successfully, but these errors were encountered: