Znafon

6 ms·

1.
by Znafon 3y ago
"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 was to publish the code on Github." I’m
2.
by Znafon 3y ago
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 it wouldn't be applicable? Would the details
3.
by Znafon 3y ago
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 scripts to control those activities". Then i
4.
by Znafon 3y ago
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 is not exactly clear from the license.
5.
by Znafon 3y ago
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 list the registered function with math_exprs.keys() and that mi
6.
by Znafon 3y ago
Oh yeah, that’s right! Thanks for the correction
7.
by Znafon 3y ago
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 single string. Variadic fun
8.
by Znafon 3y ago
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 neither the existence or uniqueness of shuch sheep, so it rais
9.
by Znafon 3y ago
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:])
10.
by Znafon 3y ago
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 and has no utility beyond that. I'm not sure what spco
11.
by Znafon 3y ago
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?
12.
by Znafon 3y ago
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.
13.
by Znafon 3y ago
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 hard / impossible, but I'
14.
by Znafon 3y ago
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 work from Eric Snow has been merged, you can use https:/&
15.
by Znafon 3y ago
> 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 is shipped in Python 3.12. The results are very impressiv
16.
by Znafon 3y ago
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 want the maximum performance of single th
17.
by Znafon 3y ago
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 the "Container Thread-Safety" (I think container
18.
by Znafon 3y ago
Would the work on sub-interpreters be interested for that then ( https://lwn.net/SubscriberLink/941090/8bcb029dbf548f26/ ) ?
19.
by Znafon 3y ago
> 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/multiprocessing, is that sometimes you don't want queues
20.
by Znafon 3y ago
The performance patches have already been merged and there is ongoing working in the Faster CPython project.
21.
A Per-Interpreter GIL(lwn.net)
2 points by Znafon 3y ago|0 comments
22.
by Znafon 3y ago
Sentry has not been using BSL since the beginning.
23.
by Znafon 3y ago
> 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 looks like a good model for OSS,
24.
by Znafon 3y ago
Isn't that what email and mailing lists are for?
25.
by Znafon 3y ago
Yes, you can do this: https://pip.pypa.io/en/stable/topics/vcs-support/
26.
Lolwut: A piece of art inside a database command(antirez.com)
1 points by Znafon 3y ago|0 comments
27.
by Znafon 3y ago
This is quite an oversimplification. Some modules have no active maintainers and take time from the small team that work on CPython. Some modules are deprecated and removed to make it possible to allocate time on other improvements, and the
28.
The Art of PostgreSQL(theartofpostgresql.com)
3 points by Znafon 3y ago|0 comments
29.
by Znafon 4y ago
I’m referring to the easy looking, tricky to solve problems. I’ve heard them referred to by that term because they have been used at Moscow University to discriminate against Jewish students but I don’t know if they have other names. There
30.
by Znafon 4y ago
That’s a very elegant solution. Hard looking problems that had simple, trick solutions were called Jewish Problems at the entrance of some universities. This would let the examiner fail a student for subjective reasons instead of academic s

More ›