rasterio v1.2.0

[regro-cf-autotick-bot]

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

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
   Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

NEW: If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

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. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot.
The regro-cf-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!
This PR was generated by https://github.com/regro/autotick-bot/actions/runs/508018089, please use this URL for debugging}

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis of the source code shows a discrepancy between the library's imports and the package's stated requirements in the meta.yaml.

Packages found by inspection but not in the meta.yaml:

• gdal

Packages found in the meta.yaml but not found by inspection:

• libgdal

[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.

[snowman2]

@conda-forge-admin, please rerender.

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.

[snowman2]

For Windows & Python 3.6:

(%PREFIX%) %SRC_DIR%>python -m pytest -v -m "not wheel" -rxXs -k "not (test_hit_ovr or test_file_in_handler_with_vfs or test_files or test_parse_windows_path or test_copyfiles_same_dataset_another_name or test_context)" tests 
ImportError while loading conftest 'D:\bld\rasterio_1611540418406\test_tmp\tests\conftest.py'.
tests\conftest.py:17: in <module>
    import rasterio
..\_test_env\lib\site-packages\rasterio\__init__.py:9: in <module>
    from rasterio._base import gdal_version
E   ImportError: DLL load failed: The specified procedure could not be found.

@ocefpaf any ideas? Is this a blocker to merging now?

[ocefpaf]

@ocefpaf any ideas? Is this a blocker to merging now?

We are on the verge to drop py36, so no. Let's merge.

[snowman2]

We are on the verge to drop py36

That's good to know. Is there a tracking issue for that?

[ocefpaf]

That's good to know. Is there a tracking issue for that?

Nope. We are planning on adopting NEP 29 for all of conda-forge. The only hiccup was the pypy builds that relied on Python 3.6. Now that we have pypy 3.7 we are discussing that again. It probably won't happen overnight but it is in our sights.