Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Is upload_or_check_non_existence.py needed?

See original GitHub issue

I’m trying to understand the purpose of upload_or_check_non_existence.py. FWICT we may just be better served by setting anaconda_upload to true in .condarc. This will ensure that packages get uploaded. We can configure the token to use when we build. There may be some kinks to work out, but I’d rather spend time doing that than maintaining a nearly identical copy of this functionality in every feedstock.

cc @msarahan @pelson

Issue Analytics

State:
Created 7 years ago
Comments:12 (12 by maintainers)

Top GitHub Comments

1reaction

pelsoncommented, Aug 24, 2016

I’d rather spend time doing that than maintaining a nearly identical copy of this functionality in every feedstock

FWIW, I’m keen to move this out of each feedstock too - there is an issue somewhere for it, but I can’t find it right now. The quickest intermediate step is to put the same script (with modifications) into a common repo (conda-forge-build-setup?) from which we can get this functionality. Longer-term I’m definitely interested in whether we can achieve the same functionality with conda-build’s upload (when I wrote this, we couldn’t) though.

0reactions

pelsoncommented, Sep 29, 2016

We have moved the upload script to the conda-forge-build-setup.