Skip to content

We should look at upgrading segment-analytics-python #52514

Closed

Description

@potiuk

Currently Airlfow holds it back from upgrading

Activity

  1. converted this from a draft issue on Jun 30, 2025
  2. changed the title [-]segment-analytics-python should[/-] [+]We should look at upgrading segment-analytics-python[/+] on Jun 30, 2025
  3. eladkal commented on Jun 30, 2025

    @eladkal
    Contributor

    Already handled #52401

  4. potiuk commented on Jun 30, 2025

    @potiuk
    MemberAuthor
    --- Explaining for analytics-python (current: 1.2.9, latest: 1.4.post1) ---
      uv sync output for analytics-python==1.4.post1:
      warning: The release specifier (`~=3.10`) contains a compatible release match without a patch version. This will be interpreted as `>=3.10, <4`. Did you mean `~=3.10.0` to freeze the minor version?
        × No solution found when resolving dependencies for split
        │ (python_full_version == '3.12.*' and platform_machine == 'x86_64' and
        │ sys_platform == 'darwin'):
        ╰─▶ Because apache-airflow depends on analytics-python==1.4.post1 and
            analytics-python==1.4.post1 depends on backoff==1.10.0, we can conclude
            that apache-airflow depends on backoff==1.10.0.
            And because segment-analytics-python>=2.3.1 depends on backoff>=2.1
            and segment-analytics-python==2.3.0 was yanked (reason: Missing
            dependency), we can conclude that segment-analytics-python>=2.3.0 and
            apache-airflow are incompatible.
            And because only the following versions of segment-analytics-python
            are available:
                segment-analytics-python<=2.3.0
                segment-analytics-python==2.3.1
                segment-analytics-python==2.3.2
                segment-analytics-python==2.3.3
                segment-analytics-python==2.3.4
            and apache-airflow-providers-segment depends on
            segment-analytics-python>=2.3.0, we can conclude that
            apache-airflow-providers-segment and apache-airflow are
            incompatible.
            And because your workspace requires apache-airflow and
            apache-airflow-providers-segment, we can conclude that your workspace's
            requirements are unsatisfiable.
      
            hint: While the active Python version is 3.10, the resolution failed for
            other Python versions supported by your project. Consider limiting your
            project's supported Python versions using `requires-python`.
    

    Ah .. Interesting so we need to check why https://github.com/apache/airflow/blob/constraints-main/constraints-3.10.txt still contains analytics-python if it is removed.

  5. self-assigned this
    on Jun 30, 2025
  6. potiuk commented on Jun 30, 2025

    @potiuk
    MemberAuthor

    Likely #52599 should help

  7. eladkal commented on Jun 30, 2025

    @eladkal
    Contributor

    analytics-python shouldn't be there. It was replaced by segment-analytics-python

  8. potiuk commented on Jun 30, 2025

    @potiuk
    MemberAuthor

    analytics-python shouldn't be there. It was replaced by segment-analytics-python

    Yes. And I already found out why - because we were checking against PyPI providers only:

    If you look here - https://github.com/apache/airflow/blob/constraints-main/constraints-3.10.txt - it is still there because this one is built using packages from PyPI - and the change merged in main is NOT yet released to PyPi - all the segment providers available in PyPI still use "analytics-python"

    But when you look here: https://github.com/apache/airflow/blob/constraints-main/constraints-source-providers-3.10.txt - > analytics-python is missing (good) - because it does not use PyPI, it uses local pyproject.tomls that already do not have PyPI.

    This is where #52606 is going to be useful because it will show 9 (!) reports - with different combinations of:

    • python versions
    • types of constraints (constraints - PyPI, constraints-source-providers -> pyproject.toml files, constraints-no-providers -> only airflow + source preinstalled providers
  9. potiuk commented on Jun 30, 2025

    @potiuk
    MemberAuthor

    i think we can close this one. After #52606 is merged we wil be able to see different reports and this one will be missing.

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

Metadata

Metadata

Assignees

Labels

area:dependenciesIssues related to dependencies problems

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions