Add xyzspaces

[deeplook]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml"
• License file is packaged (see here for an example)
• Source is from official source
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged)
• If static libraries are linked in, the license of the static library is packaged.
• Build number is 0
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details)
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there

[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/xyzspaces) and found it was in an excellent condition.

[deeplook]

Since I am posting this PR I am also willing to be listed here... ;)

[deeplook]

I see in the Azure pipeline logs that fiona is used, but not declared as a requirement. Which is weird because on Travis-CI there this is building fine. Maybe the conda builds are in some sense stricter, and if so I'd like to know in which one?

[synapticarbors]

conda-forge isn't building for pytho<3.6, so you can remove the skip and use noarch: python:

https://conda-forge.org/docs/maintainer/knowledge_base.html#noarch-python

you can always add the version restrictions under requirements (i.e change python to python >=3.6 under host and run)

[synapticarbors]

You need to add everything in the setup.py's install_requires, which looks to be read out of:

https://github.com/heremaps/xyz-spaces-python/blob/master/requirements.txt

I'm guessing the issue with fiona not being on the list, but being required is that it is a dependency of one of the listed dependencies, so it gets picked up. Just a guess though

[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/xyzspaces) and found some lint.

Here's what I've got...

For recipes/xyzspaces:

• requirements: host: turfpy>=0.0.3 must contain a space between the name and the pin, i.e. turfpy >=0.0.3

[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/xyzspaces) and found it was in an excellent condition.

[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/xyzspaces) and found some lint.

Here's what I've got...

For recipes/xyzspaces:

• Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

[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/xyzspaces) and found it was in an excellent condition.

[deeplook]

I don't seem to put the pip-only dependencies like "turfpy" and "geobuf" at the right place. When trying to run conda smithy recipe-lint . locally I get "No azure token. Create a token and put it in ~/.conda-smithy/azure.token. Running out of ideas...

Maybe this is still relevant, which seems to suggest I cannot list pip-only dependencies in a recipe? conda/conda-build#548 and conda-forge/conda-forge.github.io#28.

[synapticarbors]

@deeplook - we don't really want any pip-only dependencies. We'll need to open separate pull requests for turfpy and geobuf and get those merged before we can move forward with this recipe.

[deeplook]

@synapticarbors While I can imagine the reasoning (stability, etc.) behind not wanting to support plain pip packages (which is somewhat ironic, as pip is still needed, I believe), I have failed to see a bold argument like this made on https://conda-forge.org/docs/index.html. I think this could help people spend more time on relevant things (like convincing other maintainers to publish their packages on conda-forge). What do you think?

[synapticarbors]

@deeplook -- I've submitted a pull request (#12514) to address the missing dependencies.

[deeplook]

I see https://github.com/conda-forge/turfpy-feedstock and https://github.com/conda-forge/geobuf-feedstock now. Awesome, thanks!

[synapticarbors]

@deeplook -- I restarted the build in this PR and it looks like linux is now passing. Just waiting on the others.

[synapticarbors]

@deeplook -- can you confirm that the other co-maintainers have agreed to be listed? Otherwise they should comment here saying they are.

[deeplook]

@synapticarbors I confirm.

[deeplook]

@synapticarbors Anything else I need to do? Otherwise this is ready for review.

[deeplook]

Thanks!

[deeplook]

@synapticarbors BTW, the description field on https://anaconda.org/conda-forge/xyzspaces is empty despite the description given in the meta.yaml file. Am I missing something?

[synapticarbors]

No packages on conda-forge have that populated (e.g https://anaconda.org/conda-forge/numpy). The description shows up in https://github.com/conda-forge/xyzspaces-feedstock#about-xyzspaces