Thanks! Good to know.

This is an example. For my actual use case, they would be private vars that would be set by class functions instead of passed to the constructor.

Implicit optional is deprecated. Explicitly use self.foo: int | None = None

Why not require values in the constructor?

That seems like that's going to give you an error in most type checkers. You said it's always an int and then immediate made that a lie and made it None instead.

Why are you trying to do this?

Just a random update for any late comers. Decided to use git (and self host via forgejo). Absolutely lost in git, but this video was remarkably helpful for broad concept. https://youtu.be/e9lnsKot_SQ

well... it's a bit hard to say considering that the sort of style this library encourages is pretty unpythonic. if i did something similar i'd probably make a wrapper type that has all the functionality as methods, which would necessarily require compartmentalisation. i'd probably break it up into one file fore everything with related functionality and compose the final type from that.

Thank you.

Remeda.js was organised like this. How would you organise it?

it's a really cool proof of concept, and i hope to never encounter it in the wild.

also, why is this organised with one function per file?

project cost = sigma(1...n)(risk likelihood of occurring * risk cost), but we aren't discussing every possible risk. Only the one risk.

The risk of having to:

• for the app to work, requires compiled components
• having to be familiar with setup.py. This is referred to as the sewer, which is what is targeted by hackers e.g. xv
• maintainers who come later being familiar and can maintain packages that incorporate other languages e.g. C or rust
• possibly neglecting to perform the compile (but lets ignore this)
• compiler runs a binary written and maintained by the spy agency Google

or

Just not doing that

The only justification for going with protoc, over other methods, could only come down to data serialization speed. But in that case, wouldn't a rust solution be: not only as fast, but also much safer.

It's a potential single point of failure. Which have experienced first hand. The rest of the app could not run cuz a non-essential piece was non-operable due to the missing compiled message definitions file or message definitions file was updated but not compiled.

So protobuf carries a non-zero risk.

Could the app have been designed without an essential exploding binary blob? Most definitely yes!

A better approach

That unfortunately isn't a better approach. The compilation step requires protobuf to be installed, by the distro package manager. To my knowledge it's not available from pypi.

An uncompiled protobuf file is essentially worthless unless it's compiled. But if it's compiled then it's a binary blob.

Not anti-protobuf. Just make the protobuf compiler available without getting a distro package manager involved.

Otherwise slower alternatives might be more viable.

strictyaml bundles strictyaml.ruamel, which used to be an external unmaintained C package.

This reduces strictyaml dependencies to:

pyproject.toml

dependencies = [
    "python-dateutil>=2.6.0"
]

Just that one. So can be confident strictyaml will work.

Can the same be said for protobuf and Google (over invested in AI and is probably dying underneath a huge debt burden while spending tons of money on AI wash propaganda while not funding Python projects enough. Maintainer leave or burn out while everyone is too busy head fcking us with the AI washing to notice.)

Also there is strictyaml that validates against schemas. Don't touch the builtin yaml module.

protobuf needs to be compiled. This introduces possibility of coder error. Just forgetting to compile and commit protobuf files after a change. This affected the electrum btc and ltc (light) wallets.

It can yes, but you may also run it as a separate process via a manage.py command. The scheduler will also work in either set up, and locks itself to running just once. So it's safe to scale any way want.

cool, does that mean it runs in the same event loop as the asgi server?

I second this.

The thing is, none of the suggested alternatives can do what pickle does, and the article focuses on a narrow (albeit ubiquitous) use case: serialisation of untrusted data.

There are still legitimate use cases for pickle, especially when storing, caching, or comparing objects that can't easily be serialised with say, JSON or TOML. It's a question of using the right thing for the right job is all, and pretending like JSON is a comparable alternative to pickle doesn't help anyone.

code goes in git which you can push to other devices and pull from other devices. but if you're not used to it and you turn off a machine and forget to push... you're stuck.

for syncing files in general, I use syncthing. open source, e2e encrypted.

if you are new to git, these sources might help:

1. https://git-scm.com/book/en/v2 - number one source, available online, for free, has complete translation to quite a few languages

• https://learngitbranching.js.org/
• https://girliemac.com/blog/2017/12/26/git-purr/
• https://firstaidgit.io/#/
• https://git-scm.com/docs

Ah, haven't heard of that before. Thanks for your reply, I'll look into it :)

Thanks for your reply, I definitely have to look up the best practices for git storage / branches etc as I have no idea. Pretty keen to distance myself from Microsoft where able.