MagicStack / MagicStack/asyncpg
DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
* **asyncpg version**: 0.22.0
* **PostgreSQL version**: local `postgres:13-alpine` via Docker
* **Python version**: 3.9.1
* **Platform**: macOS 11.2.3; Linux 4.19.121 (via Docker Desktop for Mac)
* **Do you use pgbouncer?**: no
* **Did you install asyncpg with pip?**: via poetry
The following warning is produced when running a [simple CRUD example from SQLAlchemy's docs](https://docs.sqlalchemy.org/en/14/orm/examples.html#examples-asyncio):
```
/usr/local/lib/venv/someproject-asdfqwer-py3.9/lib/python3.9/site-packages/asyncpg/connect_utils.py:544: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
tr, pr = await loop.create_connection(
```
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 at asyncpg/connect_utils.py around line 544 and reproduce the warning using the SQLAlchemy asyncio CRUD example linked in the issue. Check how the connection is created and verify that the example no longer emits the Python 3.9 deprecation warning while preserving the connection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100