Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

⬆️(dependencies) update python dependencies #2514

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 14, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
black (changelog) ==24.8.0 -> ==24.10.0 age adoption passing confidence
ipython ==8.27.0 -> ==8.28.0 age adoption passing confidence
mysqlclient ==2.2.4 -> ==2.2.5 age adoption passing confidence
psycopg2-binary (source, changelog) ==2.9.9 -> ==2.9.10 age adoption passing confidence
pylint-django ==2.5.5 -> ==2.6.1 age adoption passing confidence
sentry-sdk (changelog) ==2.14.0 -> ==2.17.0 age adoption passing confidence

Release Notes

psf/black (black)

v24.10.0

Compare Source

Highlights
  • Black is now officially tested with Python 3.13 and provides Python 3.13
    mypyc-compiled wheels. (#​4436) (#​4449)
  • Black will issue an error when used with Python 3.12.5, due to an upstream memory
    safety issue in Python 3.12.5 that can cause Black's AST safety checks to fail. Please
    use Python 3.12.6 or Python 3.12.4 instead. (#​4447)
  • Black no longer supports running with Python 3.8 (#​4452)
Stable style
  • Fix crashes involving comments in parenthesised return types or X | Y style unions.
    (#​4453)
  • Fix skipping Jupyter cells with unknown %% magic (#​4462)
Preview style
  • Fix type annotation spacing between * and more complex type variable tuple (i.e. def fn(*args: *tuple[*Ts, T]) -> None: pass) (#​4440)
Caching
  • Fix bug where the cache was shared between runs with and without --unstable (#​4466)
Packaging
  • Upgrade version of mypyc used to 1.12 beta (#​4450) (#​4449)
  • blackd now requires a newer version of aiohttp. (#​4451)
Output
  • Added Python target version information on parse error (#​4378)
  • Add information about Black version to internal error messages (#​4457)
ipython/ipython (ipython)

v8.28.0

Compare Source

PyMySQL/mysqlclient (mysqlclient)

v2.2.5

Compare Source

What's Changed

New Contributors

Full Changelog: PyMySQL/mysqlclient@v2.2.4...v2.2.5

pylint-dev/pylint-django (pylint-django)

v2.6.1

NOTICE


We dropped support for Python 3.7, 3.8, and for pylint below 3.0.

Bugfixes
  • Added Django aliases for ranges to support psycopg 2 and 3 (#&#8203;421 <https://github.com/pylint-dev/pylint-django/pull/421>_)
  • Support for Python 3.12 datetime (#&#8203;427 <https://github.com/pylint-dev/pylint-django/pull/427>_)
  • Fixed location of installed LICENSE file (#&#8203;431 <https://github.com/pylint-dev/pylint-django/issues/431>_)
  • Fixed ForeignKeyStringChecker referencing linter config incorrectly (#&#8203;430 <https://github.com/pylint-dev/pylint-django/issues/430>_)

Other


- CI now tests against Django 5.1
getsentry/sentry-python (sentry-sdk)

v2.17.0

Compare Source

Various fixes & improvements

v2.16.0

Compare Source

Integrations
  • Bottle: Add failed_request_status_codes (#​3618) by @​szokeasaurusrex

    You can now define a set of integers that will determine which status codes
    should be reported to Sentry.

    sentry_sdk.init(
        integrations=[
            BottleIntegration(
                failed_request_status_codes={403, *range(500, 600)},
            )
        ]
    )

    Examples of valid failed_request_status_codes:

    • {500} will only send events on HTTP 500.
    • {400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.
    • {500, 503} will send events on HTTP 500 and 503.
    • set() (the empty set) will not send events for any HTTP status code.

    The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.

  • Bottle: Delete never-reached code (#​3605) by @​szokeasaurusrex

  • Redis: Remove flaky test (#​3626) by @​sentrivana

  • Django: Improve getting psycopg3 connection info (#​3580) by @​nijel

  • Django: Add SpotlightMiddleware when Spotlight is enabled (#​3600) by @​BYK

  • Django: Open relevant error when SpotlightMiddleware is on (#​3614) by @​BYK

  • Django: Support http_methods_to_capture in ASGI Django (#​3607) by @​sentrivana

    ASGI Django now also supports the http_methods_to_capture integration option. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is ("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",). OPTIONS and HEAD are not included by default.

    Here's how to use it:

    sentry_sdk.init(
        integrations=[
            DjangoIntegration(
                http_methods_to_capture=("GET", "POST"),
            ),
        ],
    )
Miscellaneous

v2.15.0

Compare Source

Integrations
  • Configure HTTP methods to capture in ASGI/WSGI middleware and frameworks (#​3531) by @​antonpirker

    We've added a new option to the Django, Flask, Starlette and FastAPI integrations called http_methods_to_capture. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is ("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",). OPTIONS and HEAD are not included by default.

    Here's how to use it (substitute Flask for your framework integration):

    sentry_sdk.init(
        integrations=[
          FlaskIntegration(
              http_methods_to_capture=("GET", "POST"),
          ),
      ],
    )
  • Django: Allow ASGI to use drf_request in DjangoRequestExtractor (#​3572) by @​PakawiNz

  • Django: Don't let RawPostDataException bubble up (#​3553) by @​sentrivana

  • Django: Add sync_capable to SentryWrappingMiddleware (#​3510) by @​szokeasaurusrex

  • AIOHTTP: Add failed_request_status_codes (#​3551) by @​szokeasaurusrex

    You can now define a set of integers that will determine which status codes
    should be reported to Sentry.

    sentry_sdk.init(
        integrations=[
            AioHttpIntegration(
                failed_request_status_codes={403, *range(500, 600)},
            )
        ]
    )

    Examples of valid failed_request_status_codes:

    • {500} will only send events on HTTP 500.
    • {400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.
    • {500, 503} will send events on HTTP 500 and 503.
    • set() (the empty set) will not send events for any HTTP status code.

    The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.

  • AIOHTTP: Delete test which depends on AIOHTTP behavior (#​3568) by @​szokeasaurusrex

  • AIOHTTP: Handle invalid responses (#​3554) by @​szokeasaurusrex

  • FastAPI/Starlette: Support new failed_request_status_codes (#​3563) by @​szokeasaurusrex

    The format of failed_request_status_codes has changed from a list
    of integers and containers to a set:

    sentry_sdk.init(
        integrations=StarletteIntegration(
            failed_request_status_codes={403, *range(500, 600)},
        ),
    )

    The old way of defining failed_request_status_codes will continue to work
    for the time being. Examples of valid new-style failed_request_status_codes:

    • {500} will only send events on HTTP 500.
    • {400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.
    • {500, 503} will send events on HTTP 500 and 503.
    • set() (the empty set) will not send events for any HTTP status code.

    The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.

  • FastAPI/Starlette: Fix failed_request_status_codes=[] (#​3561) by @​szokeasaurusrex

  • FastAPI/Starlette: Remove invalid failed_request_status_code tests (#​3560) by @​szokeasaurusrex

  • FastAPI/Starlette: Refactor shared test parametrization (#​3562) by @​szokeasaurusrex

Miscellaneous

Configuration

📅 Schedule: Branch creation - "before 7am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Dependency-related tasks. label Oct 14, 2024
@renovate renovate bot force-pushed the renovate/python-dependencies branch 4 times, most recently from 83dfd39 to cb5e0ad Compare October 18, 2024 09:56
@renovate renovate bot force-pushed the renovate/python-dependencies branch from cb5e0ad to cd9bc4a Compare October 20, 2024 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Dependency-related tasks.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants