Demo project for building and deploying a Python+Cython packages with AppVeyor CI and Travis CI.
This is based on a similar demo: https://github.com/theochem/python-appveyor-conda-example Additional features:
Less auxiliary scripts, making more use of recent Travis and AppVeyor built-in features. This should be easier to understand and adapt.
Conda packages for win-32, win-64, linux-64, osx-64.
Python 2.7, 3.5, 3.6.
Upload to alpha, beta and main channels on Anaconda cloud.
Github stable and prerelease source release.
PyPI source release. Stable releases only stable only, because others are not safe to upload to PyPI.
Documentation deployment to gh-pages (Travis).
CI Testing after installation on Travis or AppVeyor instance.
Code coverage with codecov.io.
The CI machinery in this project is “easily” used in other projects. The following files/parts need to be copied over (and modified):
- The version stuff from setup.py and pycydemo/__init__.py. This extracts the version from the latest git tag. Ideally, no other places in your project should define (another) version. Also mind the following in setup.py:
zip_safe=False (for nosetests and conda packaging) See https://github.com/nose-devs/nose/issues/1057
Order of importing setuptools and Cython matters.
Copy tools/conda.recipe/meta.yaml and change the package name and dependencies.
Copy .travis.yml and update the env block, including new encrypted tokens and passwords.
For windows testing: copy .appveyor.yml and update the env block, including new encrypted tokens and passwords.
Making tokens:
Github: https://github.com/settings/tokens (scopes repo:public_repo)
- Anaconda: https://anaconda.org/theochem/settings/access Scopes:
api:read (Allow read access to the API site)
api:write (Allow write access to the API site)
Encrypting tokens (Github, Anaconda) and passwords (PyPI) on Travis-CI:
Basic documentation: https://docs.travis-ci.com/user/encryption-keys/
Best usage is to just run travis encrypt without arguments. Then enter a variable and content in the form VAR=pass. Press enter. Press Ctrl-d.
Copy the encrypted stuff to the env section of .travis.yml
Encrypting tokens (Anaconda) and passwords on AppVeyor:
Only enter the password or token itself, so only the pass part of VAR=pass. The VAR is still visible in .appveyor.tml``.
Copy to .appveyor.yml.
Metadata
Release files for pycydemo 0.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pycydemo-0.3.5.tar.gz | 3.2 kB | Without provenance | Details for pycydemo-0.3.5.tar.gz |
Release files / pycydemo-0.3.5.tar.gz
| Download URL | pycydemo-0.3.5.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
119a9faf86b6e67ca2d858da7229a89ae8344a28478dfdb562bee5f32b127157
|
|
BLAKE2b-256 checksum How to use checksums |
0263fce9c0e05cfe783882a7d259c41d1cdc386d7834cf9b154bfe0d7fbaf12c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pycydemo 0.3.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.