The ruling makes for excellent reading. Anyone has a right to their beliefs, but professing those beliefs is not protected if they are not "worthy of respect in a democratic society, being not incompatible with human dignity and not conflicting with the fundamental rights of others". In terms of the paradox of tolerance, it's a remarkable bit of good sense.
Maya Forstater was the name IIRC; that doesn't spring readily to mind but that line really stuck.
Not fired; the woman in question was on a fixed contract which wasn't renewed when it came to an end, because she was bullying and acting like an unpleasant arse.
The judgement was careful and thoughtful, but was glossed as "you can't even say you're a woman without going to prison these days". When you read about a judgement that sounds so bizarre as to be unbelievable, there is a good chance (in the UK at the least) that it didn't say what is reported. (Cf. "We can't deport terrorists because it's against their pet cat's human rights".) Social media is a machine for making people insane. The rest is history.
That'd be Dame Cressida Dick, later promoted to Commissioner of the Met.
Developers aren't the ones at fault here.
Possibly the thing that was intended to be deployed was. What got pushed out was 40kB of all zeroes. Could've been corrupted some way down the CI chain.
The government plan was struck down by the high courts here because Rwanda was not a suitable destination according to the ECHR.
The (previous) government's response was (a) to pass a law declaring that it was a safe destination; (b) to look to limit the ability of the courts to rule on the legality of government policy.
They really were unconscionably unpleasant fuckers.
Check Crowdstrike's blurb about the 1-10-60 rule.
You can bet that they have a KPI that says they can deliver a patch in under 15m; that can preclude testing.
Although that would have caught it, what happened here is that 40k of nuls got signed and delivered as config. Which means that unparseable config on the path from CnC to ring0 could cause a crash and was never covered by a test.
It's a hell of a miss, even if you're prepared to accept the argument about testing on the critical path.
(There is an argument that in some cases you want security aystems to fail closed; however that's an extreme case - PoS systems don't fall into that - and you want to opt into that explicitly, not due to a test omission.)
The plan rather blurred "illegal immigrant" and "legitimate asylum seeker".
[[[ ...specifically garbage collection (GC) is really really fast compared to some other languages (I’m looking at you Java) ]]]
... Really? This is quite a claim - does anyone have references to the details behind this?
...unless it's running software that uses signed 32-bit timestamps, or stores data using that format.
The point about the "millennium bug" was that it was a category of problems that required (hundreds of) thousands of fixes. It didn't matter if your OS was immune, because the OS isn't where the value is.
Personation DOES NOT HAPPEN. Voter ID disenfranchises; there's no fraud its preventing.
Yeah, thise were two things directly aimed at the misbehaviour of the outgoing government.
Ah, those heady days, before shouting "nonsense!" at Jack Straw would gwt you arrested under the (woefully badly-written) Prevention of Terrorism Act. It's almost as though power corrupts (and the office of the Home Sec in particular is enough to break the morals of anyone).
The specific things I recall were the FOIA (which Blair later came to regret; the tine to strike with such things is while the fires of idealism still burn hot) and removing the control of interest rates from the Treasury - the Tories had been royally fucking the economy with that in the years running up to the election. Imagine if Truss had her hands on that lever.
The "why" is that the import system is caching modules in sys.modules.
The "what to do about it" is "not this". Use a package layout with explicit names (p1.generic_name etc) instead.
You can use relative imports under those packages if you prefer (from .generic_name import ...).
If you want executables on the path look at setup.py or any of the myriad of overlapping modern equivalents that'll let you specify a command-libe executable to install, then pip install -e . to install it in your venv's bin dir.
Here's another. You being you isn't a line of defence if someone decides to murder you on a date.
Serious answer then: you won't be fired for being yourself.
When I had this conversation with a trans mate (who had a fucking awful Daily Heil-reading co-worker with no notion of what was appropriate conversation for the workplace) I said, "hang on a moment, isn't [being fired over being out] illegal?" He said, "yes, but it doesn't stop it happening."
I believed him - he was living it, he had the experience. Conversations with him involved me getting smacked in the face with my own privilege on a regular basis. You have it easy.
If things are changing a bit each month, then in your module rather than a plain variable assignment
darabase = ...
you might want a function that you can pass in parameters to represent the things that can change:
def database(dir, ...):
...
return ...
Then you can call it like this:
from database import database
db = database("/some/path")
... gope that makes some sense.
If it is the first thing, just put the db setup code you're using in one file, call it "database.py"
# the code you commonly use, ending with
database = ...
From a second file in the same directory, write: main_program.py
from database import database
# The first "database" here is the module name.
# The second "database" is a variable you set inside that module.
# You can also write this as follows:
# import database
# ... and use `database.database` to refer to the same thing
# but that involves "stuttering" throughout your code.
# use `database` as you would before - it refers to the "database" object that was found in the "database.py" module
then run it with python main_program.py
The main thing to realise here is that there are two names involved. One's the module, the other is the variable (or function name) you set inside that module that you want to get access to.
There's not much here to go on. Are you asking how to write a module that you can import?
Are these the same set of DB files every time? Are the columns and other configurations the same? Are you writing new python code every month?
Are you using some ETL process to spit out a bunch of files that you'd like to have imported and available easily? Are the formats the same but the filenames differ?
I think it's the first thing you're after. There are a bunch of tutorials knocking around about this, eg, https://www.digitalocean.com/community/tutorials/how-to-write-modules-in-python-3
You might also be asking: if I write a module, how do I make it available for all my new python projects to use? You could just copy your whatever-my-module-is-called.py file around to your new projects (this might be simplest) but if you're also expecting to be updating it and would like all of your projects to use the updated code, there are alternatives. One is to add the directory containing it to your PYTHONPATH. Another is to install it (in edit mode) in your python environment.
[I get the impression you're a data person rather than a programmer - perhaps you have a colleague who's more of the latter you can tap up for this? It doesn't have to be difficult, but there's typically a little bit of ceremony involved in setting up a shared module however you choose to do it.]
Ken Livingston (back when he was mayor) famously referred to the US Ambassador as a "chiselling little crook" for the continued nonpayment of fines (I think it was in the millions even then).