Update the conda package in conda-forge

[motybz]

It seems that the latest conda package of gql is 2.0.0
https://anaconda.org/conda-forge/gql/files
Can you please upload the latest one? (3.1.0)
Can you please add it to the release automation?

[bollwyvl]

There is already a (failing) automated PR for this: conda-forge/gql-feedstock#10

I'll see if i can get it cleaned up and merged.

[leszekhanusz]

All the conda stuff was made before I became maintainer. I suppose I'll need some access code or something. I'll see with the previous guys to see how we can proceed.

[motybz]

Thank you guys, please let me know if there is anything that I could help with.

[leszekhanusz]

Pinging @KingDarBoja

[bollwyvl]

how we can proceed.

I'll be following up on the conda-forge side once a release goes out with #311 in it. I'll ensure that it runs pip check and the test suite under coverage with a threshold, which is usually good enough for enable automerge.

when i get that working, I can ping you: it's always good to have upstream-aware maintainers around! you'd just need to comment that you'd like to be a maintainer, and get added to a file.

if the existing maintainers are unresponsive (life happens), we can escalate to the conda-forge core team, but hopefully it doesn't come to that.

After a PR gets merged adding you as a maintainer, the workload would be:

• wait for a notification about a bot making a PR after a pypi release
  • if it's auto-merge, and everyhting's green, then there's nothing to do
• if dependencies changed or tests failed
  • change a few lines of yaml
  • type a comment on a PR
• repeat until ✔️
• press a button on PR

[bollwyvl]

#311 is now in, so when the next release goes out, i'll work on overhauling the conda-forge build.

[leszekhanusz]

Version 3.2.0 is now released.

[bollwyvl]

Thanks for the heads-up, I've started the PR over there:

conda-forge/gql-feedstock#12

If you'd like to help maintain (usually just means pressing button, maybe updating a dep or two), I can add you as well: just make a comment over there to that effect.

[bollwyvl]

That PR was merged, and should be available within an hour or two on CDN: feel free to open another issue to propose another maintainer.

[leszekhanusz]

Great!

[motybz]

Thank you very much, it works.
I think it is worth writing in the documentation that extra dependencies not included in the conda package installation recipe (like websocket)

[bollwyvl]

Yeah, conda lacks extras, the best we have are run_constrained, which we

use to honor at least extras that have version constraints. To actually light up the dependencies, we build a bunch of metapackages e.g. graphql-with-websockets. They are all listed on the graphql-feedstock github page, but not the anaconda.org page for graphql, but would be found by search. It's hard to be too sad about not having extras, given the issues they present: they aren't discoverable on pypi (at all) or locally, short of reading the setup data, and user+selected ones aren't honored in later resolves. Message ID: ***@***.***>

…

[leszekhanusz]

I added some documentation on PR #321