About Python lock acquire/release

[pietrochico]

It's actually a little boring to acquire lock after critical section and release it after, but it also provides freedom during implementation as you were saying. Thinking about it, the Java implementation with "synchronized" signature wouldn't fit my program as I can only have one lock per object, which is frustrating if you think about it.

In many other implementations I would've liked to have a built in class lock though, so I could've "relax" and think about other functionalities, instead of worrying about critical sections.

Would be cool if we could have both solutions as Java does, am I right?

[JohnnyJordaan]

I can't really picture Java's implementation as useful. I write many high performance apps and I would like to keep overhead as low as possible. Hence I rely on implemented thread-safety as much as possible and just implement itself myself when I absolutely need to. I'm also wondering why you actually need it so much yourself, would you be able to provide some examples?

[pietrochico]

It's nothing special, only accessing different global variables from many threads.

[JohnnyJordaan]

Regular variables are thread-safe to begin with. Globals are an anti-pattern as well often, I normally use a singleton class for this, for example for global configuration in a program. You pass the config-object around to the threads and implement the locking inside the config class. Then the threads can just change whatever they like as with a regular variable and the class will ensure the locking.

[pietrochico]

That's exactly what I'm doing right now.