Skip to content

Bump pytest from 8.3.4 to 8.3.5#27

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/pytest-8.3.5
Open

Bump pytest from 8.3.4 to 8.3.5#27
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/pytest-8.3.5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Mar 8, 2025 •
edited by sourcery-ai Bot
Loading

Copy link
Copy Markdown

Bumps pytest from 8.3.4 to 8.3.5.

Release notes

Sourced from pytest's releases.

8.3.5

pytest 8.3.5 (2025-03-02)

Bug fixes

  • #11777: Fixed issue where sequences were still being shortened even with -vv verbosity.
  • #12888: Fixed broken input when using Python 3.13+ and a libedit build of Python, such as on macOS or with uv-managed Python binaries from the python-build-standalone project. This could manifest e.g. by a broken prompt when using Pdb, or seeing empty inputs with manual usage of input() and suspended capturing.
  • #13026: Fixed AttributeError{.interpreted-text role="class"} crash when using --import-mode=importlib when top-level directory same name as another module of the standard library.
  • #13053: Fixed a regression in pytest 8.3.4 where, when using --import-mode=importlib, a directory containing py file with the same name would cause an ImportError
  • #13083: Fixed issue where pytest could crash if one of the collected directories got removed during collection.

Improved documentation

  • #12842: Added dedicated page about using types with pytest.

    See types{.interpreted-text role="ref"} for detailed usage.

Contributor-facing changes

  • #13112: Fixed selftest failures in test_terminal.py with Pygments >= 2.19.0
  • #13256: Support for Towncrier versions released in 2024 has been re-enabled when building Sphinx docs -- by webknjaz{.interpreted-text role="user"}.
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Bump pytest from 8.3.4 to 8.3.5 to pick up bug fixes and documentation improvements.

Bug Fixes:

  • Fix issue where sequences were still being shortened even with -vv verbosity.
  • Fix broken input when using Python 3.13+ and a libedit build of Python.
  • Fix AttributeError crash when using --import-mode=importlib when top-level directory same name as another module of the standard library.
  • Fix a regression in pytest 8.3.4 where, when using --import-mode=importlib, a directory containing py file with the same name would cause an ImportError.
  • Fix issue where pytest could crash if one of the collected directories got removed during collection.

Documentation:

  • Add dedicated page about using types with pytest.

@dependabot
Bump pytest from 8.3.4 to 8.3.5
aded3c6 
Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.3.4 to 8.3.5.
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@8.3.4...8.3.5)

---
updated-dependencies:
- dependency-name: pytest
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Mar 8, 2025
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Mar 8, 2025 •
edited
Loading

Copy link
Copy Markdown

Deploying pyzn with  Cloudflare Pages  Cloudflare Pages

Latest commit: aded3c6
Status: ✅  Deploy successful!
Preview URL: https://c22698c9.pyzn.pages.dev
Branch Preview URL: https://dependabot-pip-pytest-8-3-5.pyzn.pages.dev

View logs

@dependabot dependabot Bot mentioned this pull request Mar 8, 2025
Closed
@sourcery-ai

sourcery-ai Bot commented Mar 8, 2025 •
edited
Loading

Copy link
Copy Markdown

Reviewer's Guide by Sourcery

This pull request updates the pytest dependency from version 8.3.4 to 8.3.5. This is achieved by modifying the Pipfile.lock file to reflect the new version.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Bumped the version of the pytest dependency.
  • Updated pytest from version 8.3.4 to 8.3.5 in Pipfile.lock.
 Pipfile.lock
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Mar 8, 2025

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

sourcery-ai[bot]
sourcery-ai Bot reviewed Mar 8, 2025
View reviewed changes

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

@codiumai-pr-agent-free

codiumai-pr-agent-free Bot commented Mar 8, 2025 •
edited
Loading

Copy link
Copy Markdown

CI Feedback 🧐

(Feedback updated until commit aded3c6)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: Tests

Failed stage: Start environment [❌]

Failure summary:

The action failed because the docker-compose command was not found in the system path. When trying
to execute make start-containers, the command attempted to run docker-compose but received a
"/bin/sh: 1: docker-compose: not found" error, causing the make command to fail with exit code 127
(command not found).

Relevant error logs: 
1:  ##[group]Operating System
2:  Ubuntu
...

428:  Logging into ghcr.io...
429:  Login Succeeded!
430:  ##[group]Run DOCKER_TAG=sha-$GITHUB_SHA make start-containers
431:  �[36;1mDOCKER_TAG=sha-$GITHUB_SHA make start-containers�[0m
432:  shell: /usr/bin/bash -e {0}
433:  ##[endgroup]
434:  PYZN_VERSION=sha-83bbe647a0cd2a2ae99dbb77b0367943c94153ac docker-compose -f infrastructure/docker-compose.yml --project-directory . up -d
435:  /bin/sh: 1: docker-compose: not found
436:  make: *** [Makefile:6: start-containers] Error 127
437:  ##[error]Process completed with exit code 2.

@sonarqubecloud

sonarqubecloud Bot commented Mar 8, 2025

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

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

Reviewers

@sourcery-ai sourcery-ai[bot] sourcery-ai[bot] left review comments

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file python Pull requests that update Python code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants