# Fix "DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead" in a Python Library

Yes. An agent finds every logger.warn call, reproduces the DeprecationWarning under -W error, renames each to logger.warning, runs the tests and opens a PR.

[Run this on Rush](https://cloud.getrush.ai/run/fix-the-warn-method-is-deprecated-use-warning-instead/logging/). Opens the console with this prompt ready to send, in a Project that has your repository.

## What the agent does

The agent clones the repository into its own cloud sandbox and reads the logging setup before changing anything. In a single-module library like studioimaginaire/phue, the Philips Hue client at 1.2, `phue.py` creates `logger = logging.getLogger('phue')` on line 33 and uses it throughout; a search for `logger.warn(` finds eleven calls, among them the colour-temperature setters at lines 251, 253, 266 and 269 (`'6500 K is max allowed color temp'`) and the bridge error reports in `set_light`, `get_sensor` and `set_group` around lines 903, 981, 1026 and 1113, next to two calls that already use `logger.warning(` at lines 167 and 175. `tox.ini` runs `py.test` with `pytest-timeout` and coverage plus a `pep8` env that runs `flake8 phue.py`; `test-requirements.txt` lists `pytest`, `pytest-cov`, `pytest-timeout` and `testtools`, and of the two files under `tests/`, `test_basic_import.py` imports the module and `test_request.py` mocks `http.client.HTTPConnection` around `Bridge.request`.

Then it reproduces the warning. `Logger.warn` has printed `DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead` since Python 3.3 and still does on 3.13, but only when warnings are shown: the agent runs an interpreter with `-W default`, builds a `Light` over a fake bridge object whose `get_light` returns a colour temperature, and sets `colortemp_k = 9000`, which prints the warning from line 266. With `-W error::DeprecationWarning` the same statement raises instead of logging, which is how a test suite run with `-W error`, or a monitoring rule that counts `DeprecationWarning` lines, surfaces it. The existing five tests pass under both flags because none of them reaches a `warn` line.

The fix is the rename: each `logger.warn(` becomes `logger.warning(`, eleven lines in `phue.py` and nothing else, leaving thirteen `logger.warning(` calls. The agent then repeats the `colortemp_k = 9000` check under `-W error::DeprecationWarning`: it now logs `WARNING:phue:6500 K is max allowed color temp` and clamps the value to 6500 K, stored as 154 mireds, with no exception. The five tests still pass under the same flag, and the agent adds one test for that clamp so the path is covered from now on.

It reports what the run showed but did not change. `flake8 phue.py` already fails on three `E302` lines (51, 58, 65) before this change, so the `pep8` env is red independently of it; `setup.py` imports `distutils.core`, which Python 3.12 removed from the standard library and which `pip` still supplies through setuptools; and the tests mention Python 2 fallbacks that no supported interpreter takes. Each goes in the pull request as a finding with its line.

## Start it with one API call

`POST https://api.phoenix.so/o/{org}/sessions`

```json
{
  "agent": "claude",
  "input": "The library prints `DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead`. List every logger.warn and logging.warn call with its file and line. Reproduce the warning by calling one of those code paths under python -W default, and show that under -W error::DeprecationWarning it raises. Rename each call to warning, keeping the message and arguments as they are. Run the existing tests under -W error::DeprecationWarning before and after, add one test that exercises a renamed call path, and quote the results. Report any other failing check you notice, such as the lint env, with its line and without fixing it. Open a pull request that quotes the reproduction and both test runs.",
  "resources": [
    {
      "url": "https://github.com/your-org/your-app"
    }
  ]
}
```

1. **Get an API key.** In the console, open Settings, then API keys, and create a key for your org. Send it in the Authorization header as a Bearer token.
2. **Send the request.** POST the body in request.json to https://api.phoenix.so/o/{org}/sessions, with your repository as the resources URL. The run starts in its own cloud sandbox.
3. **Read what came back.** Follow the run on its live stream or wait for the run.completed webhook, then read the result and its trajectory.

## What comes back

What comes back is a pull request touching `phue.py` and one test file: eleven `logger.warn(` calls renamed to `logger.warning(` with their messages untouched, and a new test that sets a colour temperature past the limit and asserts the clamp and the logged warning. The description lists the eleven lines, quotes the `DeprecationWarning` from the `-W default` run and the exception from the `-W error` run, and shows the tests passing under `-W error::DeprecationWarning` after the change.

A reviewer checks that no message string changed, that the diff holds no other edit, and that the findings list keeps the pre-existing `flake8` failures and the `distutils` import out of this change. The run's record holds the reproduction and both test runs, so the before and after can be opened rather than taken on trust.

## Run it on every log alert for a DeprecationWarning

Add an automation to the repository's Project with a `webhook` trigger and this prompt, and point a Grafana contact point at the trigger's URL with `Authorization: Bearer <its secret>` as a custom header, fed by an alert rule that matches `DeprecationWarning` in the service's logs. Each firing alert starts one run that lists the deprecated calls behind the warning and opens a pull request; a warning from a dependency rather than the repository's own code ends with a report that names the package.

Grafana retries a delivery it could not confirm, so send an `Idempotency-Key` on the trigger's URL made from the alert's fingerprint and the run is started once. The automation's own `max_runs_per_hour` bounds a noisy rule.

## Why run it on Rush?

A deprecation that only prints when warnings are shown is invisible on a laptop with the default filter, and the first time it matters is in a CI job run with `-W error` or in a log alert. The agent reproduces it under both filters in its own sandbox and keeps every run in the record, so the pull request shows the warning and its absence rather than describing them.

The rename is mechanical, but the proof that nothing else changed is the suite under `-W error::DeprecationWarning` plus a test that actually reaches a renamed call, which this library did not have. Doing both in one run gives a reviewer a diff of eleven lines and a test that would catch the next `warn`.

## Frequently asked questions

### Will Python remove Logger.warn?

It has been deprecated since Python 3.3 and is still present in 3.13, where it prints the same warning. A removal would turn every remaining call into an `AttributeError`, which is why the rename is worth doing while it is still only a warning; `warning` has been the documented name all along.

### Why does my test suite not show the warning?

Python's default filter hides `DeprecationWarning` outside `__main__`, and a test only prints it when the test reaches the call. The agent runs the reproduction with `-W default`, and the suite with `-W error::DeprecationWarning`, so a reached `warn` fails the run rather than scrolling past.

### Does logging.warn at module level have the same problem?

Yes. The module-level `logging.warn()` prints `The 'warn' function is deprecated, use 'warning' instead` and is renamed the same way. The agent's list covers both forms, so a repository that mixes them gets one pull request.

### What if the warning comes from a dependency?

Then the file in the warning's location is under `site-packages`, and the fix belongs upstream. The agent names the package and version in its report instead of patching the installed copy, and the pull request, if any, covers only the repository's own calls.

## More jobs like this: Fix a bug from an alert

- [Fix "AttributeError: 'Thread' object has no attribute 'isAlive'" on Python 3.9+](https://getrush.ai/run/fix-thread-isalive-attribute-error/threading/)
- [Fix "AttributeError: module 'time' has no attribute 'clock'" on Python 3.8+](https://getrush.ai/run/fix-time-clock-attribute-error/time/)
- [Fix "_pickle.UnpicklingError: Weights only load failed" from torch.load in PyTorch 2.6 and Later](https://getrush.ai/run/fix-torch-load-weights-only-unpickling-error/pytorch/)
- [Fix "AttributeError: module 'tornado.web' has no attribute 'asynchronous'" after a Tornado upgrade](https://getrush.ai/run/fix-tornado-web-asynchronous-attribute-error/tornado/)
- [Fix CryptographyDeprecationWarning: TripleDES Has Been Moved in a Paramiko Tool](https://getrush.ai/run/fix-tripledes-cryptography-deprecation-warning/paramiko/)
- [Fix "AttributeError: module 'tweepy' has no attribute 'StreamListener'"](https://getrush.ai/run/fix-tweepy-streamlistener-attribute-error/tweepy/)

## Keep reading

- [How a Rush run works on your repository, from request to pull request](https://getrush.ai/cloud/)
- [Compare cloud agents, agent sandboxes and AI code review](https://getrush.ai/compare/)
- [Rush pricing: Free, Pro and Max](https://getrush.ai/pricing/)
