Viewing profile — Znafon

"Nothing came of it, but I took the code and shoved it into my back pocket for a rainy day. My idea was to take this code and spruce it up for Uber’s use case." "My first reaction …

The AGPL says "including scripts to control those activities" but if I understand what you are saying properly it means that the text of the AGPL is overreaching and some parts of …

The AGPL defines "Corresponding Source" as "all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scri…

It's not just big tech that hates AGPL. If Terraform was under AGPL a lot of companies might have to release their source code as AGPL too because of its virality. Where it stops i…

You could modify it easily, for example the user could register an additional function to the mapping. That would not be as easy to do with a module and getattr(). You can also lis…

Oh yeah, that’s right! Thanks for the correction

I'm not sure print(firstname, lastname) for example is more readable than print((firstname, lastname)) especially since I would then have to write print((surname,)) to just print a…

I think it is consistent, it works a bit like filtering an element from a mathematical set. Given a set of sheeps, let x be the five-legged sheep is inconsistent because we know ne…

It is used when the number of argument can vary, like: def sum(*args: int) -> int: if len(args) == 0: return 0 return args[0] + sum(*args[1:])

spacectl, vcs-agent and terraform-provider-spacelift are only useful with your proprietary product. prometheus-exporter is a very small exporter to monitor your proprietary product…

So the software from your company is fully closed-source, isn't it? The employes can do open-source on Friday but no part of Spacelift is actually open-source?

This is a very non-charitable read of the history here. Also, none of the companies that pledge FTE support to OpenTF are open-source.

The PEP goes into details about the motivations and why the single thread model has limitations: https://peps.python.org/pep-0703/#motivation . > Yes, some applications will remain…

They were always usable using the C-API but not exposed to the Python library (and until 3.12 you were blocked by the shared GIL so there was little point anyway). Now that the wor…

> I would be fine with have it never be removed, and I think we should try sub-interpreter first. There is a lot of work going on with sub-interpreters and the per-interpreter GIL …

I think you can make a non thread-safe list by just making the same object without the lock described at https://peps.python.org/pep-0703/#container-thread-safety if you really wan…

Yes this is a thing was trivially protected by the GIL. There is the same thing with mutating the same map concurrently in Go that will panic for example. PEP 703 goes over this in…

Would the work on sub-interpreters be interested for that then ( https://lwn.net/SubscriberLink/941090/8bcb029dbf548f26/ ) ?

> If you need concurrency at the moment, you have already switched to using multiprocessing, so having a no-GIL multithreading is useless. > The only issue with Python/multiprocess…

The performance patches have already been merged and there is ongoing working in the Faster CPython project.

Sentry has not been using BSL since the beginning.

> What's wrong with monetization? You understand that OSS's significant problem is a lack of funding, where authors don't want or don't know how to monetize their product? > Sentry…

Isn't that what email and mailing lists are for?

Yes, you can do this: https://pip.pypa.io/en/stable/topics/vcs-support/