Inside the lambda expression you can have a comprehension to unpack the keys list to get the same sort of uplet as your “manual” example, like this:
>>> items = [{"core_name": "a", "label": "b"},{"core_name": "c", "label": "d"}, ]
>>> keys = ["core_name", "label"]
>>> tuple(items[0][k] for k in keys)
('a', 'b')
>>> sorted(items, key=lambda d: tuple(d[k] for k in keys))
[{'core_name': 'a', 'label': 'b'}, {'core_name': 'c', 'label': 'd'}]
By “Syslog-ng Engineer” do they mean a C systems programmer who can fix bugs and add features to syslog? that’s a rather different role from being an admin; even if, depending on the size of the operation, it make sense to give both roles to the same person
Besides Journal not being available on non-Linux, there are a could of reasons for using syslog: it can log to a remote server for instance. Journal does have a remote logging capability, but at best you have to run two log sinks in parallel, at worse it’s a non starter because everything that’s not a Linux box (network routers, VMware hosts, IDS appliances) can’t speak to it
Another is fine filing and retention. With syslog you can say things like “log NOTICE and above from daemon XYZ to XYZ.log and keep 30 days worth; log everything including DEBUG to XYZ-debug.log, keep no more than 10MB”. With Journal you rotate the entire log or nothing, at least last I looked I couldnt find anything finer. There are namespaces, but that doesn’t compowe, the application needs to know which log goes into which namespace
Well I’m not missing the point then, that’s good to know :)
Maybe I’m wildly misunderstanding something, not helped by the fact that I work very little with Web technologies, but…
So, in a RESTful system, you should be able to enter the system through a single URL and, from that point on, all navigation and actions taken within the system should be entirely provided through self-describing hypermedia: through links and forms in HTML, for example. Beyond the entry point, in a proper RESTful system, the API client shouldn’t need any additional information about your API.
This is the source of the incredible flexibility of RESTful systems: since all responses are self describing and encode all the currently available actions available there is no need to worry about, for example, versioning your API! In fact, you don’t even need to document it!
If things change, the hypermedia responses change, and that’s it.
It’s an incredibly flexible and innovative concept for building distributed systems.
Does that mean only humans can interact with a REST system? But then it doesn’t really deserve the qualifier of “application programming interface”.
CVS is the authoritative repository of code, and they recommend to users to use that or reposync (built atop of CVS) to keep their system updated.
There is also a GitHub mirror , and got is an OpenBSD project, and I suspect a number of devs use one of those for local work until it’s time to push the changes to the authoritative tree.
Justification I’ve heard is that if one part of the couple is managing the other, or is promoted after the relationship started, then:
Companies will want to both avoid this sort of things, and avoid being seen to enable this sort of things. They might want to move one of the parties to a different department so that the higher up one doesn’t make promotion decisions for the other.
I’ve once worked at a company that wanted to know about relationships between their employees and suppliers/customers’ employees, again because that might enable situations where a supplier / customer is treater favourably because of personal relationships
And Fabrice Bellard, the original author of ffmpeg, went on to create qemu which pretty much made open-source virtualization possible. Also TCC (even if I don’t think that one is widely used), he established a world record for computing decimals of Pi using a single machine that had ~2000× less FLOPS than the previous record, and so much more…
I recently discovered
git commit --fixup=abcd1234: it will make a new commit with a message offixup! <message from abcd1234>. (It’s the only special thing that flag does: a specially formatted commit message, which you can craft yourself if you remember the spelling of thefixup!marker.)When you later rebase,
git rebase --interactive --autosquashwill automatically mark that commit to be a fixup ofabcd1234.magit for emacs has shortcut for creating a fixup commit selecting the previous commit, I’m sure other interfaces do too.
I’ve found that too, which I think is because as the project matures, you’re more likely to make fixes or contained features, as opposed to regular “change everything” as you explore the design in a young project.