Add recipes for trio and async_generator

[nicoddemus]

No description provided.

[conda-forge-linter]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/async_generator, recipes/trio) and found some lint.

Here's what I've got...

For recipes/async_generator:

• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• Recipe maintainers should be a json list.
• The recipe license should not include the word "License".

For recipes/trio:

• The recipe license should not include the word "License".

[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 (recipes/async_generator, recipes/trio) and found it was in an excellent condition.

[nicoddemus]

@conda-forge/staged-recipes I believe this is ready for review/merge. 👍

[isuruf]

This is unreadable. I would just take a paragraph or 2 and avoid the examples

[nicoddemus]

Fixed, thanks

[nicoddemus]

I agree, this was generated by conda build. Will change it later. Em sáb, 3 de fev de 2018 13:19, Isuru Fernando <notifications@github.com> escreveu:

…

***@***.**** commented on this pull request. ------------------------------ In recipes/async_generator/meta.yaml <#5080 (comment)> : > + - setuptools + run: + - python + +test: + imports: + - async_generator + - async_generator._tests + +about: + home: https://github.com/python-trio/async_generator + license: MIT + license_family: MIT + license_file: '' + summary: Async generators and context managers for Python 3.5+ + description: ".. image:: https://img.shields.io/badge/chat-join%20now-blue.svg\n <https://img.shields.io/badge/chat-join%20now-blue.svg%5Cn> :target: https://gitter.im/python-trio/general\n :alt: Join chatroom\n\n.. image:: https://img.shields.io/badge/docs-read%20now-blue.svg\n\ <https://img.shields.io/badge/docs-read%20now-blue.svg%5Cn%5C> This is unreadable. I would just take a paragraph or 2 and avoid the examples — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5080 (review)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABCO_L_7bkZj9rsclqsoIf7MHZozLiucks5tRHkIgaJpZM4R3gLi> .

[CJ-Wright]

Can we get a license?

[nicoddemus]

Opened python-trio/async_generator#11 and added a link to the recipe so we can fix that in the next release.

[nicoddemus]

@CJ-Wright @isuruf ready for another review.

[nicoddemus]

cc @conda-forge/staged-recipes

[ocefpaf]

Minor comments that should not prevent this from getting merged.

[ocefpaf]

This line can be dropped.

[nicoddemus]

Done

[ocefpaf]

We are moving to script: python -m pip install --no-deps --ignore-installed .. See conda-forge/conda-forge.github.io#518

[nicoddemus]

Done

[ocefpaf]

You don't need the empty field but that does not hurt.

[nicoddemus]

I prefer to leave it there so we fill it with the license file in the next release

[ocefpaf]

Kind of big and with some escape characters that I don't think are needed.

[nicoddemus]

Done

[ocefpaf]

@nicoddemus What do you want to do about the AppVeyor failure? async_generator is noit building on py27:

Processing c:\bld\async_generator_1517761572846\work\async_generator-1.9
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "c:\users\appveyor\appdata\local\temp\1\pip-msxyjb-build\setup.py", line 1, in <module>
        from pathlib import Path
    ImportError: No module named pathlib
    
    ----------------------------------------

[nicoddemus]

async_generator and trio are py35+ only, so they are not supposed to be built in py27. async_generator is noarch: python, which is why it fails to build on py27.

Should I make async_generator not noarch: python so it doesn't try to build on py27?

[ocefpaf]

You can leave the noarch there and add a constraint like python >2.7 for build and run.
Pinging @jjhelmus here who suggested that just to comfirn I got it right.

[nicoddemus]

You can leave the noarch there and add a constraint like python >2.7 for build and run.

Ahh good idea, done!

[nicoddemus]

Thanks @ocefpaf!