trio_asyncio v0.10.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.
Notes and instructions for merging this PR:

1. Please check that the dependencies have not changed.
2. Please merge the PR only after the tests have passed.
3. Feel free to push to the bot's branch to update this PR if needed.
4. The bot will almost always only open one PR per version.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one.

_{This PR was created by the cf-regro-autotick-bot.
The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, feel free to drop us a line if there are any issues!}

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[dhirschfeld]

@conda-forge-admin, please rerender

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-webservice.

I tried to re-render for you, but it looks like there was nothing to do.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[dhirschfeld]

On gitter it was suggested that the problem is packages being installed from defaults because the latest click-7.0 package doesn't have the gcc7 label applied.

The following NEW packages will be INSTALLED:

    click:                7.0-py36_0                        
    conda-forge-ci-setup: 2.1.1-py36_0           conda-forge

@conda-forge/core - assuming this is the problem, could someone please apply the gcc7 label to the latest click package?

[ocefpaf]

@conda-forge/core - assuming this is the problem, could someone please apply the gcc7 label to the latest click package?

Looks like someone already did:

https://anaconda.org/conda-forge/click/files?version=7.0

[dhirschfeld]

@ocefpaf - the click/gcc7 angle appears to have been a red-herring.

I've removed the use of pip as you suggested in conda-forge/betse-feedstock#10 (comment) so we'll see if that makes a difference...

[jjhelmus]

I believe the issues with pip are coming from the setting of PIP_NO_INDEX variable. This is done by conda-build automatically starting in version 3.17.0, see conda/conda-build#3109. I'm still trying to work out exactly what is triggering the error but disabling this configuration by changing the install line to:

script: "PIP_NO_INDEX=False {{ PYTHON }} -m pip install . --no-deps --ignore-installed --no-cache-dir -vvv"

Allows the pip based install to succeed.

[ocefpaf]

Thanks for the exaplanation @jjhelmus!

Ping @nicoddemus who also noticed this earlier today.

[jjhelmus]

Further investigation leads me to believe that anything that has a pyproject.toml file will have problems with PIP_NO_INDEX=True.

[dhirschfeld]

Thanks @ocefpaf & @jjhelmus for figuring it out!

If there are no objections I'll go ahead and merge this and when the upstream issue is fixed I can revert back to using pip again...

[dhirschfeld]

For ref, upstream issue is conda/conda-build#3318