Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #88408 > unrolled thread
| Started by | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| First post | 2015-03-31 19:44 -0400 |
| Last post | 2015-03-31 19:44 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Lockfile hanling Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-03-31 19:44 -0400
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Date | 2015-03-31 19:44 -0400 |
| Subject | Re: Lockfile hanling |
| Message-ID | <mailman.3.1427845511.12925.python-list@python.org> |
On Tue, 31 Mar 2015 16:50:12 +0200, Ervin Hegedüs <airween@gmail.com>
declaimed the following:
>Hello,
>
>there is an app, written in Python, which stores few bytes of
>datas in a single file. The application uses threads. Every
>thread can modify the file, but only one at a time. I'm using a
>lock file to prevent the multiple access.
>
If there is only one instance of the application, and it is truly using
threads...
The solution, to my mind, is to use a Python lock object around the
code that tries to modify the file.
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
Back to top | Article view | comp.lang.python
csiph-web