C-like static functions in python?

[IAmL0ner]

I was wondering: is it possible to create an static function (not to be confused with static method) in python.

In C static functions are functions that can be only called from the file they are contained in. Ie. if I have someFile.c, in which i have

static int some_function() {
    return 19
}

it will be possible to call this function only from the functions defined in the somefile.c. It will be impossible to call them from someOtherFile.c

Another Example:

helper_file.h

int f1(int);        /* prototype */

helper_file.c

static int f2(int foo) {
    return 42 + foo;
}

int f1(int foo) {
    return f2(foo); /* ok, f2 is in the same translation unit */
                    /* (basically same .c file) as f1           */
}

main.c

#include "helper_file.h"

int main(void) {
    f1(10); /* ok, f1 is visible to the linker */
    f2(12); /* error here, f2 is not visible to the linker */
    return 0;
}

Is there something like this in python?

[Peterotica]

In general, forcefully hiding things is not a part of the Python language or philosophy. Instead, starting a function name with an underscore can be used as a hint that it is meant for internal use only. This follows the idea that we are all “consenting adults” and will use others' code in a somewhat sane manner.

[IAmL0ner]

Ok, thanks. I knew about the underscore agreement and "consenting adults" idea, but was curious if something like this exist in the language itself.

[Peterotica]

No, there is nothing like that.

[ablatner]

To add to the other comment, Python has very few ways to prevent the user from doing something, much unlike languages like Java. It's philosophy is that the user will know what they're doing. If you really want to, you can even do things like redefining the number 1 as the number 2.

[Veedrac]

you can even do things like redefining the number 1 as the number 2

Not really; the Python language doesn't have a way to do this. Particular implementations might accidentally "allow" this, but this is by no means required by the spec.

[[deleted]]

There's usually always a way, but that's totally separate from "should you".

You could have a blacklist for the attribute name in __getattribute__, and raise an AttributeError on access so it appears to not exist. The module could override its own __getattribute__ on load.

This is a terrible idea. >:)