Skip to content

Conversation

@ahms5
Copy link
Member

@ahms5 ahms5 commented Feb 11, 2025

fixes all deprecation warnings in #36

@ahms5 ahms5 requested a review from mberz February 11, 2025 14:30
@ahms5 ahms5 added this to the v1.0.0 milestone Feb 11, 2025
@ahms5 ahms5 added the v1.0.0 label Feb 11, 2025
]
dependencies = [
'pyfar>=0.5.0',
'pyfar>=0.6.0',
Copy link
Member Author

Choose a reason for hiding this comment

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

required for the PyfarDeprecationWarning

@f-brinkmann f-brinkmann requested a review from mberz February 21, 2025 13:45
@ahms5 ahms5 requested review from Copilot and mberz and removed request for mberz March 31, 2025 06:37
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates deprecation warnings to use PyfarDeprecationWarning throughout the codebase and synchronizes related API parameters and dependency versions.

  • Replaces DeprecationWarning with PyfarDeprecationWarning for functions, tests, and internal warnings
  • Adjusts the parameter name from freq_range to frequency_range in a function call to align with the updated API
  • Upgrades the pyfar dependency from version 0.5.0 to 0.6.0

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
tests/test_dsp.py Removed several tests related to impulse response start functionality
tests/test_deprecation_warnings.py Updated tests to expect PyfarDeprecationWarning instead of DeprecationWarning
pyrato/roomacoustics.py Switched to PyfarDeprecationWarning for deprecation messages
pyrato/edc.py Minor reformatting adjustments in numerical computations
pyrato/dsp.py Updated warnings to use PyfarDeprecationWarning and renamed a parameter
pyproject.toml Updated pyfar dependency version to >=0.6.0
Comments suppressed due to low confidence (2)

tests/test_dsp.py:20

  • Several tests for find_impulse_response_start have been removed from this file; please ensure that critical behavior continues to be tested elsewhere.
def test_start_ir_insufficient_snr():

pyrato/dsp.py:332

  • The parameter is now passed using 'frequency_range' instead of 'freq_range'. Please double-check that this change correctly matches the updated API of pf.dsp.filter.fractional_octave_bands.
return pf.dsp.filter.fractional_octave_bands(

@ahms5 ahms5 changed the title fix deprecation warnings on cookiecutter pr Cookiecutter: fix deprecation warnings Mar 31, 2025
@ahms5 ahms5 removed the v1.0.0 label Mar 31, 2025
@github-project-automation github-project-automation bot moved this from Require review to Reviewer Approved in Weekly Planning Apr 13, 2025
@f-brinkmann
Copy link
Member

Are the tests failing due to changes in this branch or must something be merged to resolve this?

@f-brinkmann f-brinkmann moved this from Reviewer Approved to Require review in Weekly Planning Apr 13, 2025
@ahms5
Copy link
Member Author

ahms5 commented Apr 13, 2025

yes because the changes here are already on develop_v1.0.0 and not fixed yet:
https://github.com/pyfar/pyrato/blob/new_cookiecutter_fix_dep/pyrato/__init__.py
#46

@ahms5 ahms5 self-assigned this Apr 23, 2025
@ahms5
Copy link
Member Author

ahms5 commented May 26, 2025

these are hotfixes and potencial hot bugs on main, so this should be done on main

@ahms5 ahms5 closed this May 26, 2025
@github-project-automation github-project-automation bot moved this from Require review to Done in Weekly Planning May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants