Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pygolang pygolang
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • pygolangpygolang
  • Merge requests
  • !1

Closed
Created Jun 19, 2024 by Carlos Ramos Carreño@vnmabus
  • Report abuse
Report abuse

Fix test of warning filters in gpython.

  • Overview 3
  • Commits 1
  • Changes 1

The tests for gpython's handling of warning filters assumed that the warnings passed in the command line were located on the top of the warning filters list. This is not true in the presence of automatically imported modules that set warning filters, such as _distutils_hack, which used to filter deprecation warnings from distutils.

We fix it by comparing against a regex which allows extra filters above or below the ones we set.

Edited Jun 20, 2024 by Carlos Ramos Carreño
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fix/warning_test
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7