Skip to content

Latest version on Pypi broken? #135

Open

Description

@cameronclaero

Hi we were using graphql_server==3.0.0b7 without any issues.

with the 3.0 release on pypi, im getting the following error now:

from graphql_server import (

ImportError: cannot import name 'HttpQueryError' from 'graphql_server' (/usr/local/lib/python3.10/dist-packages/graphql_server/init.py)
2025-08-18 07:52:22,718 247 INFO odoo odoo.service.server: Stopping gracefully

I have since reverted to b7, to solve for now

Activity

  1. syrusakbary commented on Aug 18, 2025

    @syrusakbary
    Member

    Hey @cameronclaero , the API for using GraphQL-server 3.0 has changed since 3.0.0b7. Please see the examples on how to use it

  2. kaime commented on Aug 19, 2025

    @kaime

    The issue I had was with aiohttp. I had to switch from:

    from graphql_server.aiohttp import GraphQLView

    To:

    from graphql_server.aiohttp.views import GraphQLView

    If it's intentional, then I guess the docs need to be updated: https://github.com/graphql-python/graphql-server/blob/main/docs/aiohttp.md#usage

  3. ElementalWarrior commented on Aug 26, 2025

    @ElementalWarrior

    There are no releases on this repo for b8, b9, or 3.0.0. There are no tags either. I cannot find a changelog, or good place to review changes.

    As a heads up, for someone consuming a library, this starts to look like a supply chain attack when there are 3 pypi releases in one day, with no supporting docs, reference, changelog etc.

  4. KingDarBoja commented on Mar 25, 2026

    @KingDarBoja
    Contributor

    There are no releases on this repo for b8, b9, or 3.0.0. There are no tags either. I cannot find a changelog, or good place to review changes.

    As a heads up, for someone consuming a library, this starts to look like a supply chain attack when there are 3 pypi releases in one day, with no supporting docs, reference, changelog etc.

    Hi, I don't use graphql-python anymore and the one in charge is @syrusakbary, which seems inactive once again. However, it seems like they forgot to document the v3.0.0 release in the repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions