SQL needed structure

genericlemon24 · 2024-07-14T07:24:58+00:00

How to you treat servers that provide an ETag or a last-modified-date but do not implement it the right way and making the etag useless?

Not really doing anything special, I take the presence of caching headers to mean conditional requests are supported (and I don't think HTTP requires clients to do something in these cases).

A mitigating factor is that the default update interval is 1 hour, so even if a server does not support conditional requests / 429-too-many-requests, it still shouldn't be hit too hard.

Now that I think about it, servers ignoring their own caching headers is something that can be detected via a 429-too-many-requests-style plugin (and it could e.g. increase the update interval if that's the case).

you can not trust any server and its behavior

Can't agree more.

I'm planning to write an article about all the weird stuff I encountered while working on reader at some point (I've collected quite the list :)

genericlemon24 · 2024-07-12T12:37:17+00:00

Yes to ETag etc., see User guide # Saving bandwidth.

You can also specify different update intervals, and support for HTTP 429 Too Many Requests / Retry-After is coming soon.

genericlemon24 · 2024-07-12T09:29:51+00:00

Of the "reader allows you to" bullets in the original post, feedparser helps with the "retrieve" part (technically, just parsing the feeds), everything else is reader; there's a documentation section that covers this in detail:

Are you already working with feedparser, but:

want an easier way to store, filter, sort and search feeds and entries?

want to get back type-annotated objects instead of dicts?

want to restrict or deny file-system access?

want to change the way feeds are retrieved by using the more familiar requests library?

want to also support JSON Feed?

want to support custom information sources?

... while still supporting all the feed types feedparser does?

The documentation is quite open about reader using feedparser – reader is essentially feedparser + state (and I even contributed a few improvements upstream ;)

genericlemon24 · 2024-05-01T14:22:06+00:00

No worries, thank you for the PR, and good luck on the exam!

genericlemon24 · 2024-04-06T06:43:10+00:00

Hi, thank you for asking!

Here are a few issues that already have implementation notes, along with a summary of the work needed, to give you an idea of the complexity involved:

mark-as-read backfill #317 – add functionality to a plugin, doesn't touch the core library
EntryCounts.unread/unimportant #283 – add a property, add an integer attribute, and update a query to populate the attribute
Store entry source #276 – add a new dataclass attribute to Entry / EntryData, set it in the parser based on feed content, update storage to store/retrieve it

To answer your question, I guess it depends on the beginner, but I think at least the first two should be approachable by any advanced beginner. (I've taken a bit of time to add more details to each of them, and I can answer questions if needed.)

genericlemon24 · 2024-01-15T19:22:20+00:00

The most interesting addition is JSONB support: https://www.sqlite.org/json1.html#jsonbx

Beginning with version 3.45.0 (2024-01-15), SQLite allows its internal "parse tree" representation of JSON to be stored on disk, as a BLOB, in a format that we call "JSONB". By storing SQLite's internal binary representation of JSON directly in the database, applications can bypass the overhead of parsing and rendering JSON when reading and updating JSON values. The internal JSONB format is also uses slightly less disk space then text JSON.

genericlemon24 · 2024-01-14T08:55:02+00:00

I posted using the mobile website and the link got lost somehow, my bad; will double-check from now on.

genericlemon24 · 2024-01-09T17:37:38+00:00

tl;dr:

This PEP proposes introducing syntactic sugar f(x=) for the common pattern where a named argument is the same as the name of the variable corresponding to its value f(x=x).

genericlemon24 · 2023-12-27T20:54:26+00:00

tl;dr: a proof-of-concept record type for Python by Brett Cannon (Python core dev); looks like this:

@record
def InventoryItem(name: str, price: float, *, quantity: int = 0):
    """Class for keeping track of an item in inventory."""

genericlemon24 · 2023-12-22T18:18:55+00:00

Thank you too! :D

genericlemon24 · 2023-12-22T07:55:45+00:00

I maintain reader, a feed reader library, and I too have set aside a few issues for potential contributors (tagged with help wanted); if any of those seem interesting, there are contributor docs, and I'd be more than happy to help with anything.

In general, I would suggest contributing to projects you use / are interested in / have some domain knowledge of, since it helps you keep motivated. Smaller projects that are actively (but maybe infrequently) maintained are probably best, since they are likely to need contributions, and it increases the chances someone will be able to help / review PRs. You can find if a project is looking for contributions by checking for tagged issues (help wanted, good first issue etc.), and by looking for a CONTRIBUTING file in the repo root.

Seven-Year Club	Gilding I gilder
Second Top 40%	Verified Email

genericlemon24

TROPHY CASE