About
PocketBase is an amazing tool to have in your developers backpack for a quick backend for your project. I found it pleasant to work with in Python but Vaphes existing Python SDK is in sync code while most of my application development is async these days. I started with a fork of Vaphes' SDK and tried to add async support but I gave up quite quickly and just started from scratch. You see the results here.
Installation
Note that this package is compatible with Python 3.11 and up. You can install this package directly from PyPi:
pip install pocketbase-async
# or if you use poetry
poetry add pocketbase-async
Usage
The API is mostly the same as the official JS SDK and the Vaphes Python SDK, with some exceptions. Authentication methods are namespaced under an extra .auth. There are some examples to help you along. More info to come.
Roadmap
See the project board for the list of planned work. See the open issues for a full list of proposed features (and known issues).
Contributing
Contributions are welcome and appreciated, be it typo-fix, feature or extensive rework. I recommend you to open an issue if you plan to spend significant effort on making a pull request, to avoid dual work or getting your work rejected if it really doesn't fit this project.
Don't forget to give the project a star! Thanks again!
- Fork the project
- Create your feature branch (
git checkout -b feat/some-nice-feature) - Commit your changes (
git commit -m 'feat: Add some AmazingFeature') - Push to the pranch (
git push -u origin feat/some-nice-feature) - Open a pull request
License
Distributed under the MIT License. See LICENSE.txt for more information.
Attributions
The pocketbase-async package was inspired and guided in implementation by several other projects:
- The official js sdk: https://github.com/pocketbase/js-sdk
- The Python SDK by Vaphes: https://github.com/vaphes/pocketbase
- The official documentation: https://pocketbase.io/docs/
Furthermore, a lot of the API tests were adapted from Vaphes' work (licensed MIT).
:arrow_up_small: Back to top
Release files for pocketbase-async 0.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pocketbase_async-0.12.0.tar.gz | 12.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pocketbase_async-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.8 kB
Release files / pocketbase_async-0.12.0.tar.gz
| Download URL | pocketbase_async-0.12.0.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b414d343a88d38d20526a3bac9d136efe1495739674ea11bb56a09e3f721f7be
|
|
BLAKE2b-256 checksum How to use checksums |
f53e1d77f4fe0193cc7355311f09c668bbd0ab38eba8a200cb107ae3afb585c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 2, 2025.
Transparency logRelease files / pocketbase_async-0.12.0-py3-none-any.whl
| Download URL | pocketbase_async-0.12.0-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
decfd5f328ef8f0002cfc7ff6da7fad789e05f14cff5404bcc1682222d202828
|
|
BLAKE2b-256 checksum How to use checksums |
74a36d05105403e141ab75f130d5a4bfe7a2dd63a4a643c5da6850cf3e5b4bc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 2, 2025.
Transparency log