That would be one of mine, probably.
http://code.google.com/p/pyxmlcheck/
It's an old version. I haven't updated it in a while.
And while my program worked fine at home, my test environment gave me some
grief. Apparently the lock files are being deleted properly. I have a few ideas
about that,
On Mon, Jul 18, 2011 at 1:33 PM, Josh English
wrote:
> Sadly, I'm the type of guy who almost has to re-invent the wheel. When I
> started XML processing, it was on an old computer and I couldn't get things
> like lxml to work, or understand the ones I did manage to install. To fully
> understan
Chris,
I got my solution working, at least on my local machine. I'm trying to bundle
it for testing on location.
I've thought about the server-client model and one day I may have the guts to
tackle that, but I don't think it's this project.
Sadly, I'm the type of guy who almost has to re-inve
On 16Jul2011 10:37, Josh English wrote:
| You use a directory as lock mechanism. I think I get how that works.
| When you're done manipulating the file, do you just remove the director?
Yes. The advantages of a directory are twofold: you can't mkdir() twice
while you can usually open the same fil
On 16Jul2011 10:34, Josh English wrote:
| I found a FileLock (lost the link and it's not in the code) that uses
| context managers to create a ".lock" file in the same directory of the
| file. It uses os.unlink to delete the .lock file but I don't know if
| this deletes the file or just removes it
Multiple clients reading from and writing to a central collection of
related data is a problem that has been largely solved. Use a
database, and have the clients act on it with transactions. There's
no reason to re-invent the wheel.
You could have the clients connect to the database directly ove
On Sun, Jul 17, 2011 at 3:41 AM, Josh English
wrote:
> Chris,
>
> Thank you for spelling this out. I thought about this as a solution but I
> don't have the skills to create this server application, and I don't know if
> the target network can handle this request. They can see files on a shared
On Fri, Jul 15, 2011 at 3:47 PM, Josh English
wrote:
> Maybe not to the gurus here, but for me, this is a complex problem and I want
> to make sure I understand the real problem.
>
> All of this is in Python 2.7 and wxPython
>
> I have several XML files on a shared drive.
> I have applications on
Chris,
Thank you for spelling this out. I thought about this as a solution but I don't
have the skills to create this server application, and I don't know if the
target network can handle this request. They can see files on a shared drive.
They can't see each other's computers on the network, a
I found a FileLock (lost the link and it's not in the code) that uses context
managers to create a ".lock" file in the same directory of the file. It uses
os.unlink to delete the .lock file but I don't know if this deletes the file or
just removes it from the directory and leaves the memory fill
Cameron,
You use a directory as lock mechanism. I think I get how that works.
When you're done manipulating the file, do you just remove the director?
Josh
--
http://mail.python.org/mailman/listinfo/python-list
On Sat, Jul 16, 2011 at 8:37 AM, Cameron Simpson wrote:
> There are two approaches to this.
> You can create a file while your umask is 0777... [or]
> My personal habit is to make a directory for the lock
Both viable options; I'd be inclined toward the second. Or, here's a
third option. Instead o
On 15Jul2011 16:03, Billy Mays
<81282ed9a88799d21e77957df2d84bd6514d9...@myhashismyemail.com> wrote:
| I remember reading that file locking doesn't work on network mounted
| drives (specifically nfs mounts), but you might be able to simply
| create a 'lock' (mydoc.xml.lock or the like) file for th
On 07/15/2011 03:47 PM, Josh English wrote:
I remember reading that file locking doesn't work on network mounted
drives (specifically nfs mounts), but you might be able to simply create
a 'lock' (mydoc.xml.lock or the like) file for the XML doc in question.
If that file exists you could ei
14 matches
Mail list logo
