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”

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).

Once the water companies were privatised, they took out massive loans and performed no maintenance. The loans were purely to pay shareholder dividends. Now they’re loaded down with debt.

Atop this, that crumbling infrastructure can’t handle the increased water flow that’s due to rainfall increases. So there’s been a general trend of dumping raw sewage into rivers (the fines are cheaper op ex than the capex needed to fix the situation).

It’s parasitic capitalism at its finest.

Incidentally, this kind of passive-aggressive pressure is the kind of thing that might be considered a legitimate security threat, post xz. If you need to vent, vent in private. If “it works for you” but the maintainer is asking legitimate questions about the implementation, consider engaging with that in good faith and evaluating their questions with an open mind.

Which mantra is that? The ellipsis doesn’t offer a clue.

Casey’s video is interesting, but his example is framed as moving from 35 cycles/object to 24 cycles/object being a 1.5x speedup.

Another way to look at this is, it’s a 12-cycle speedup per object.

If you’re writing a shader or a physics sim this is a massive difference.

If you’re building typical business software, it isn’t; that 10,000-line monster method does crop up, and it’s a maintenance disaster.

I think extracting “clean code principles lead to a 50% cost increase” is a message that needs taking with a degree of context.

The issue with this is the same as with the mayoral system. The next tine the Tories get a turn, they replace it with FPTP and claim it’s “more democratic”.

What if your test is the only thing that calls a function?

It’s all the files. Content-addreasable storage means that they might not take up any more space. Smart checkout means they might not require disk operations. But it’s the whole tree.

Came here to say the same thing. The git book is an afternoon’s reading. It’s well worth the time - even if you think you know git.

People complain about the UX of the cli tool (perhaps rightly) but it’s honestly little different from the rest of the unix cli experience: ad hoc, arbitrary, inconsistent.

What’s important is a solid mental model and the vocabulary of primitive and compound operations built with it. How you spell it in the cli is just a thing you learn as you go.

Came here to mention laser cooling; glad someone else got there first.