GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Drop the support of Python 3.10 · Issue #7069 · feast-dev/feast

Drop the support of Python 3.10 #7069

New issue
Copy link
New issue
Copy link
Closed
#7101
Closed
Drop the support of Python 3.10#7069
#7101
Copy link

Description

@shuchu
shuchu
opened on Oct 25, 2026
Issue body actions

Python 3.10 's EOL is on Oct 31 2026. https://devguide.python.org/versions/

The Git workflow will not test Python 3.10 anymore.

Activity

  1. patelchaitany commented on Oct 27, 2026

    @patelchaitany
    patelchaitany
    on Oct 27, 2026
    Contributor
    More actions

    Do we have a plan for Python 3.15 support? It was released on Oct 9, 2026, and adds lazy imports (PEP 810) and a stdlib profiler (PEP 799).

  2. shuchu commented on Nov 4, 2026

    @shuchu
    shuchu
    on Nov 4, 2026
    CollaboratorAuthor
    More actions

    I don't have a concrete mind yet. let me dicuss with other maintainers.

  3. patelchaitany commented on Nov 4, 2026

    @patelchaitany
    patelchaitany
    on Nov 4, 2026
    Contributor
    More actions

    @shuchu I see the plan to drop Python 3.10 now that it's no longer maintained (#7101). Meanwhile, the 3.10 unit-test job fails on all PRs, because sqlglotc has no 3.10 wheels and the source build pulls an unpinned sqlglot that no longer compiles.
    #7104 fixes it by pinning build-time dependencies to the CI lock, and 3.10 passes there. It's harmless: the installed packages, the other Python versions and the existing setup all stay the same.
    If dropping 3.10 is going to take longer, should we merge #7104 in the meantime to unblock CI?

    Reacted by Shuchu Han
  4. shuchu commented on Nov 5, 2026

    @shuchu
    shuchu
    on Nov 5, 2026
    CollaboratorAuthor
    More actions

    I see the integration test failed. is that fine? are you going to fix them?

    I'm ok with merge #7104 first.

  5. patelchaitany commented on Nov 5, 2026

    @patelchaitany
    patelchaitany
    on Nov 5, 2026
    Contributor
    More actions

    5. I see the integration test failed. is that fine? are you going to fix them?
    I'm ok with merge #7104 first.

    Yes I am looking into Integration test failure.

  6. shuchu
    closed this as completedin #7101on Nov 6, 2026
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

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.