Skip to content

Forced Flask Version <2.1.0 Requirement Is Breaking Build #1391

@dsoprea

Description

@dsoprea

How do you use Sentry?

Sentry Saas (sentry.io)

Version

1.5.9

Steps to Reproduce

Sentry is suddenly requiring that Flask is <2.1.0 as of 1.5.9:

image

The changelog doesn't explain it:

image

The PR (#1379
) doesn't explain it, either. The commit doesn't really explain it other than to say that it's just to not break unit-tests:

(9a82f7b

image

However, this broke our build and not wanting to break Sentry's unit-tests is not an awesome reason for doing so. As a result, we're having to keep Sentry at 1.5.8 in order to unblock things. Can you explain more why this was necessary? Is there a timeline for getting this figured out so we can go back to using tip?

Dustin

Expected Result

No build conflict

Actual Result

Build conflict:

pkg_resources.ContextualVersionConflict: (Flask 2.1.1 (/usr/local/lib/python3.8/dist-packages), Requirement.parse('flask<2.1.0,>=0.11; extra == "flask"'), {'sentry-sdk'})

Metadata

Metadata

Assignees

No one assigned
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions