MagicStack / MagicStack/asyncpg
suggestion
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
is it mentioned in the doc that you don't need to close the connection when it is written in the form of async with pool.acquire() as con:
I know it is somehow obvious for python users.
but for newer python users i think it's not so clear.
even some python devs may use the with statement for the first time to make database access ,so they are not familiar with that convention .
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
The payload does not name a documentation file; search the docs for async with pool.acquire() as con: and the connection-management guidance. Update the explanation so newcomers can tell that the context manager handles release, then verify the surrounding database-pool example remains accurate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100