logging_strict @ logging_strict @programming.dev

Posts

7

Comments

217

Joined

1 yr. ago

Here is a bug fix where even a drug addict could see it's merge worthy.

Could fall off the bar stool semi-conscious and still be able to acknowledge it's merging worthy.

Just click the freak'n YES button.

Why market a package that is stuck in the WindowsXP era?

Why single out lack of docs for foreign keys? The docs do deal with one to many and many to many relationships. Step by step.

The trick is finding that page. It's there, just TOC is wonky. Unnecessarily hard to find things.

Foreign keys howto is a minor issue compared to the 70 PRs in the waiting queue.

Production? SQLModel is not production ready. I can name 70 reasons why not.

Please Sebastián bring on other maintainers with PR approval authority. Only this would be a game changer.

Probably most projects are as guilty as tiangolo. Myself included. How to scale to multiple maintainers? Tell me about your experience. Would like to know how to avoid this trap.

This seems to be a github weakness. Each of us individually contributes by making a great package. Folks start using it and situation does not scale.

Rinse wash repeat

will have to wait for py314 for that

If only would be so lucky. Truly i don't mind. Here go at

Purposefully do not have any code of conduct for any of my packages. And i have not joined python.org to avoid submitting to a code of conduct.

Everyone is welcome to be themselves. If something hurtful is said, i'll take it in stride without barraging the commenter with Captain obvious sweet nothings.

You troll, i disparage. It's not so different. Except for the two fresh super hero creation stories.

For the love of cosplay and super hero conventions, for a moment could put down those tunnel vision goggles to acknowledge the well written prose. Or not, but that's on you

Dear OP

SQLModel looks unmaintained. The PRs are languishing in purgatory waiting for the submitters to croak from old age. I died a little inside (see imdb all reviews must start with a drama queen comment like this) noticing the PR count has just achieved 70 PRs as of today. Which must be an achievement in project mismanagement.

According only from the release notes, the last real release was sqlmodel-0.0.23 on Feb 28th 2025. For those keeping score today is Aug 8th 2025

Most activity is bots upgrading gh actions and precommit autoupdate. aka commit spam.

The last human commit was Jun 19th fixing some tests for the docs.

This is a sell point for litestar. Bypassing pydantic also bypasses the horror show of SQLModel.

Will look into msgspec+litestar

Nowhere was the term, idiot, uttered. It's not an issue IQ solves. If it's possible to just submit more PRs harder this situation would only worsen. No matter how many PRs or how well intentioned.

nuance is lost cuz the details keep piling up and its overwhelming. Have mercy! Provide a checklist. At the end of the checklist write This is everything you must do. There is nothing more. You are done!

You need to learn about humility

One more thing to add to the checklist. Is that sqlalchemy create_engine params, pass through dbapi drivers params, or sqlite peculiarities humility? And ask yourself if you want to be constantly thinking if only i was more humble create_engine would always work as expected, without worries, or in this case, without reframing (the conversation).

Are you seeing my point, the guy who points others to the contributing page?

The guy in charge of random database objects names does not harbor ill-intent, the heat he is packing in his pants is sufficient, he is in no way inadequate, in one way or another.

He's overwhelmed. And along the way, nuance is lost.

The guy in charge of random database objects names is legion. And if not him, someone and something else.

Hmmm seem to have misplaced that checklist, it's gotta be around here somewhere.

btw my favorite super hero is the mustache guy from Deadpool. All time favorite.

Made a very convincing argument that what the super hero universes need is a guy with a thick mustache who just happened to show up for the interview with that stash.

That's what's been missing from every super hero team.

As far as i can tell the mustache guy seems like a good blook.

I hate good people with their good intentions, mustache guy didn't have good intentions. He just happened to want the job. Which was good enough for Deadpool.

This is why i'm nominating the guy in charge of random database object names to the team.

btw this is not off topic, read the SQLModel docs! All the examples are about super heroes and their teams. None of which i recognize cuz there also seems to be the guy who misspells super heroes and teams names

Which sorta makes sense. Anyone who'd lower case all table names would probably not be above misspelling super heroes and teams names.

Is there anything more sinister than lower casing all table names? And then ... get this ... preventing changing the table naming algo by hiding the implementation within a metaclass. Leaving the only option, to hardcode each and every table name.

Finally got to a Python question

On Nix(OS) can i setup a python development environment from requirements files without ruffling the package managers feathers?

When ready to create a wheel, python -m build, how does Nix(OS) want the python package to be built to gain all the benefits of Nix(OS) build reproducibility?

Other, maybe clearer, way to inspect references

id(a) == id(b)

Then reserve the use of is for bool or None.

Python has a concept of, Just don't do that. Which would be a great title for this topic thread.

Eww eww eww, I have a good one!

function argument: params vs **params

Assume both are the same Mapping.

The former can update in-place. The later, nope.

If the function is a generic function or one of the overloads. Wait what's that? It's the term used by functools.singledispatch to describe the fallback function when no overload function handles the case.

Anyway

Any param to either singledispatch generic or an overload, Whatever you throw at it, won't be in-place updatable.

Being able to have different package versions live side by side, is mind blowing. Most people would resort to flatpak or docker to contain that packages dependencies and transitive dependencies. But the amount of redundant packages must be mind blowing.

To not need all those redundant packages is an impressive feat!

The term is used by the trio package author. You are in for a treat! Go read the docs for trio right now! Then anyio.

Take what the trio author has to say very very seriously.

The term colored function means, in order to support concurrency, needing to modify a function with special language syntax, in this case, async.

ok fine lets talk about this Linux distro

Don't want to be a package manager database on my off hours. Why is having users manage every transitive dependency a good design?

I'm asking i really don't understand the merits of adopting this heavy burden

thank you for the history lesson

trio and anyio fixes that

One phrase not found in the article, colored functions

This is a Linux post. Has nothing to do with Python

Free threaded came on the scene and packages slowly added support. So there is a will to gravitate towards and adopt what works. Albeit gradually.

I prefer typing_extensions over typing and collections.abc

With typing_extensions, new features are always backported. With Python features, have to continuously upgrade Python. Whatever you upgrade to is already guaranteed to be very temporary. It's much easier to upgrade a package.

For the same reasoning would prefer Trio over asyncio.TaskGroup.

Which leads to the question Trio vs asyncio.TaskGroup?

asyncio.TaskGroup is a py311 feature with context kwarg added in 3.13. The documentation is very terse and i'm unsure what guarantees it has, besides strong. Missed opportunity. Could have used the adjective, Mickey mouse. Both are essentially the same, useless.

Having to upgrade to 3.13 is what i call failure to backport or simply, failure or that's what failure looks like.

Give a free pass to free threading, but everything else, no!

Having to upgrade Python to have access to sane structured concurrency is silly. Have the exact same complaints about Package Managers.

What to know about f strings

!r is a thing

!s is a thing

There is some syntax for formatting a float which will completely be forgotten that'll have to be looked up.

There is nothing else worth knowing.

Now lets moan and complain about something actually important. Like repos with languishing PRs, like SQLModel.

Upvote for the sanity check.

As the OP mentioned, this is a proposed/draft feature that may or may not ever happen.

With these kinda posts, should start a betting pool. To put money down on whether this feature sees the light of day within an agreed upon fixed time frame.

Why the commercial license for pngquant? Maybe rewriting pngcrush IP and slapping a commercial license on it is copyright infringement. This is my impression of Rust. Take others IP, rewrite it in Rust, poof copyright magically transferred. The C99 version how much of that is from prior art?

Lets just ignore prior art and associated license terms

pngquant commercial license

written by Kornel Lesiński

ImageOptim Ltd. registered in England and Wales under company number 10288649 whose registered office is at International House, 142 Cromwell Road, London, England, SW7 4EF

First commit Sep 17th, 2009

pngcrush license

Copyright (C) 1998-2002, 2006-2016 Glenn Randers-Pehrson

glennrp at users.sf.net

Portions copyright (C) 2005 Greg Roelofs