🌐 US-Proxy
class="logged-out env-production page-responsive" style="word-wrap: break-word;" >
Skip to content
This repository was archived by the owner on Sep 2, 2026. It is now read-only.
This repository was archived by the owner on Sep 2, 2026. It is now read-only.

Incompatible with latest version of google-cloud-bigquery #854

Closed

Description

@edu230991

pandas_gbq currently has unconstrained dependencies.
Yesterday a pretty key dependency like google-cloud-bigquery released a new version (https://pypi.org/project/google-cloud-bigquery/#history) which is incompatible with pandas_gbq at the moment.
I would strongly recommend constraining dependencies to avoid this in the future!

Activity

  1. parthea commented on Jan 16, 2025

    @parthea
    Contributor
  2. Linchin commented on Jan 16, 2025

    @Linchin
    Contributor

    Thanks for letting us know, looking into this.

  3. Linchin commented on Jan 16, 2025

    @Linchin
    Contributor

    Could you give me an example of how exactly they are incompatible? It would be really helpful, thanks. @edu230991

  4. tswast commented on Jan 16, 2025

    @tswast
    Contributor

    I wonder if it's related to this test failure? https://github.com/googleapis/python-bigquery-pandas/issues/855

    dtypes = {}
            for field in schema_fields:
                name = str(field["name"])
                # Array BigQuery type is represented as an object column containing
                # list objects.
    >           if field["mode"].upper() == "REPEATED":
    E           KeyError: 'mode'
    
    pandas_gbq/gbq.py:609: KeyError
    

    It seems it may have been caused by my refactor of SchemaField. https://github.com/googleapis/python-bigquery/pull/2097 where the "mode" no longer is populated to "NULLABLE" if not set.

  5. Linchin commented on Jan 16, 2025

    @Linchin
    Contributor

    Indeed, this seems to be the cause.

  6. edu230991 commented on Jan 16, 2025

    @edu230991
    Author

    That's exactly it, sorry for not being more specific

  7. Linchin commented on Jan 16, 2025

    @Linchin
    Contributor

    I will yank 3.28.0

  8. Linchin commented on Jan 16, 2025

    @Linchin
    Contributor

    3.28.0 has been yanked

  9. Linchin commented on Jan 21, 2025

    @Linchin
    Contributor

    We made a new release 3.29.0 this morning.

  10. added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    on Jan 24, 2025
  11. Linchin commented on Jan 24, 2025

    @Linchin
    Contributor

    Closing as this is fixed by googleapis/python-bigquery#2117, and we have made a new release v3.29.0 since.

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

Metadata

Metadata

Assignees

Labels

api: bigqueryIssues related to the googleapis/python-bigquery-pandas API.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions