datasette VS requests

Simon Willison's github would be a great place to get started imo -

https://github.com/simonw/datasette

I'm a fan on simonw's datasette/dogsheep ecosystem https://datasette.io/

I use Anki the exact same way. After a lifetime of learning I have accepted that I will never read over anything I write for myself voluntarily - so my two options are:

1. Write an article so good I can publish it and look it over myself later on. I did this last year with https://andrew-quinn.me/fzf/, for example.

2. Create Anki cards out of the material. Use the builtin Card Browser or even https://datasette.io/ on the underlying SQLite database in a pinch to search for my notes any time I have to.

Were you aware of, or tempted by https://datasette.io/ for creating your solution?

Browsing HN, GitHub and the like we get to see a huge variety of software products and code bases.

I often see products and think - if this product X, got together with Y, it would be pretty cool - kind of like if they had a kid together.

Not too literally, but more on the conceptual level - my level of programming is low.

E.g. Just some....

- pocketable.io & datasette (+with some more charting) [https://pocketbase.io, https://datasette.io]

You might like the Datasette project: https://datasette.io/

I don't think they are desperate for contributions but it's a welcoming environment and a fun project to hack on. You'll learn a lot just from reading the source and the incredibly informative PRs. The creator is a really talented developer with a great blog which shows up on the HN front page often.

Last year I worked through the challenges using VisiData, Datasette, and Pandas. I walked through my thought process and solutions in a series of posts.

> uploads of boring raw excel data and receive a nice UI

https://datasette.io/

For many years now, Requests has been frozen. Being left in a vegetative state and not evolving, this blocked millions of developers from using more advanced features.

- Ubiquitous “requests” library used in most docs examples, no async support https://github.com/psf/requests

Explore here.

It's Lukasa (his name is Cory, there's Łukasz in PSF though, but that's a different person). Looking at him, he made significant contributions to the requests repo: https://github.com/psf/requests/graphs/contributors

> I'd love to see the look on some of these people's faces when they find out that tool/software/whatever they use is actually using libcurl under the hood.

Python dependencies (does not include curl)

https://devguide.python.org/getting-started/setup-building/i...

The "requests" module in Python (does not use curl)

https://github.com/psf/requests

This part can be found in the README of the GitHub repository.

Looking around for similar errors I found this issue where they recommended trying to use a newer version of the urllib3 library.

but I appreciate the fact that there is an issue about it, it's acknowledged and .. unfixable, it would now break too many things https://github.com/psf/requests/issues/2002

The requests package has been the golden standard for package structure for as long as I can remember.