dropbox-sdk-python VS starlite

The creation of the dropbox-sdk-python repo was almost certainly overseen by Guido van Rossum since he was working at Dropbox at the time. There is a note in the Smartsheet SDK repo that parts of it were developed by Dropbox as well.

Or do you or should I just use this 'dropbox-sdk-python' (https://github.com/dropbox/dropbox-sdk-python)?

I'm not drawing conclusions from this, but I did some poking around..

I ran `git clone` on the repos of both rsync[0] and the official Dropbox SDK for Python[1]. I then ran sloccount on both of them.

---

rsync came in at a total of 51,410 physical source lines of code.

The Dropbox SDK came in at a total of 74,140 physical source lines of code.

---

[0] https://git.samba.org/rsync.git

[1] https://github.com/dropbox/dropbox-sdk-python

In this example, we will demonstrate how we can integrate with a third-party storage provider like Dropbox to create backups of files uploaded to Appwrite. For the sake of this example, we will be using Dropbox’s Python SDK. A similar concept applies to other API providers like Box or Google Drive. So let’s get started.

For the past one and a half years 😁. Checkout our docs https://starliteproject.dev/

#1286 is the issue tracking the removal of our last internal Pydantic datastructure, and PR #1382 has the addition of attrs based signature modelling. Once those are merged you will be able to use Starlite without Pydantic.

You can go to Open an Issue and open an issue for a feature request/enhancement and describe basically the behavior you are wanting to see.

Falcon FastAPI Sanic Starlite (disclosure: I do work here)

for server side , starliteproject.dev/, only python async framwork worth looking into.

Well, I'm not objective but I'd say Starlite (https://github.com/starlite-api/starlite) is a might fine codebase. You can also learn a lot about tooling and typing going through it.

I have mentioned your concerns to the Starlite discussions board - https://github.com/starlite-api/starlite/discussions/1183

You can find the complete changelog on our v1.51.0 GitHub release page.