Ensure deprecation warnings are shown in logs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
I noticed during Pydantic migration that deprecation warnings are not actually shown anywhere.
dataset = get_dataset(dataset_id, api_key).dict(by_alias=True)
should have issued a DeprecationWarning according to the documentation (see "migration guide"), but no warning is shown when simply spinning up the server with uvicorn main:app and querying the old/data endpoint which runs this code.
Running python -m pytest does show some deprecation warnings, but not the one for this call.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running uvicorn main:app and querying the old/data endpoint, then compare its output with python -m pytest, which shows some deprecation warnings. Trace the get_dataset(dataset_id, api_key).dict(by_alias=True) call and determine how warnings are handled in the server process. Done means the relevant deprecation warning appears in the server logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100