The ActivationPolicy
I added in an attempt to replicate what wg-quick
produces, as I recall.
The ActivationPolicy
I added in an attempt to replicate what wg-quick
produces, as I recall.
Do you notice anything wrong with my config? https://github.com/systemd/systemd/issues/30495
But you’re running Debian, so it’ll be 2 years at least before you get it.
The markdown you’re looking for is _underscores_
or *asterisks*
for emphasis.
Play store is a shitshow. It’s so hard to spot the few actual gems in the absolute avalanche of ad-ridden asset flip time wasters that have the only goal of harvesting your data or running a monero miner in the background. The chances are better with paid games, but even then it’s hit-or-miss.
I gave up on mobile gaming long ago.
You can’t expect the user to have one.
It’s only useful during development there.
Bullshit!
module/__init__.py
:
__all__ = ["foo", "bar"]
module/foo.py
:
def foo():
print("foo")
module/bar.py
:
def bar():
print("bar")
module/baz.py
:
def baz():
print("baz")
main.py
:
from module import *
from module import baz
if __name__ == "__main__":
print("main")
foo.foo()
bar.bar()
baz.baz()
Output:
$ python main.py
main
foo
bar
baz
No errors, warnings or anything.
Renders correctly for me
You could guard it.
__init__.py
:
_GUARD_SOME_UTILITY_FUNCTION = True
from .utilities import SomeUtilityFunction
utilities.py
:
def SomeUtilityFunction():
if not _GUARD_SOME_UTILITY_FUNCTION:
raise SomeException("Helpful error message")
Take this with a grain of salt, as I’m typing this on my phone and haven’t actually tried it.
Alternatively there’s the import-guard
package on PyPI. No idea if it’s any good, though. Just something a quick search brought up.
Edit:
Ok, I tried my suggestion and it doesn’t work.
That’s not correct. __all__
is not a whitelist. It is only the list used for
from module import *
If you have a module with submodules foo
, bar
and baz
and __all__ = ["foo", "bar"]
it will not prevent you from importing baz
manually. It just won’t do it automatically.
So much nomenclature in tech is watered down and obfuscated because we let marketing monkeys make decisions.
Completely agree. Ran Arch for about 10 years and had like three breakages that were all my fault (didn’t read news before a manual intervention. Once the battery died). But every time I could fix that by booting the current live image. No data loss.
It’s comparatively easy to not break things if you’re like ten years behind. 😉 But sure, Debian takes pride in its stability. I just like having recent versions of everything.
I mean, if you like knowing what your machine is doing, Arch is one of the best options.
Programmer moment.
Accidentally flashed a live image (PCBSD, IIRC) onto my 1TB external HDD instead of the thumb drive. Lost years of collected music and movies that night. I learned two things:
dd
is nicknamed ‘disk destroyer’ for good reason.It’s a pain to get anything but MacOS to run on those damn things.
You can either try to contact the seller and ask for the password or just erase the UEFI settings by shorting some jumper or something. There should be instructions how to do that for your specific model.
That’s only useful in commit messages, issue discussions and stuff like that. Why would the devs even make that execute in source files, where it’s all but guaranteed to be a false match??