Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!panix!gordon From: John Gordon Newsgroups: comp.lang.python Subject: Re: Uniquely identifying each & every html template Date: Tue, 22 Jan 2013 16:35:10 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 22 Message-ID: References: <8deb6f5d-ff10-4b36-bdd6-36f9eed58e1e@googlegroups.com> <5dd4babd-716d-4542-ad36-e6a841b73ec3@googlegroups.com> NNTP-Posting-Host: panix3.panix.com X-Trace: reader1.panix.com 1358872510 17196 166.84.1.3 (22 Jan 2013 16:35:10 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Tue, 22 Jan 2013 16:35:10 +0000 (UTC) User-Agent: nn/6.7.3 Xref: csiph.com comp.lang.python:37303 In <5dd4babd-716d-4542-ad36-e6a841b73ec3@googlegroups.com> Ferrous Cranus writes: > > If that's the case, then I figure you have about 3 choices: > > 1) use the file path as your key, instead of requiring a number > No, i cannot, because it would mess things at a later time on when i for > example: > 1. mv name.html othername.html (document's filename altered) > 2. mv name.html /subfolder/name.html (document's filepath altered) Will the file always reside on the same device? If so, perhaps you could use the file inode number as the key. (That seems fairly brittle though. For example if the disk crashes and is restored from a backup, the inodes could easily be different.) -- John Gordon A is for Amy, who fell down the stairs gordon@panix.com B is for Basil, assaulted by bears -- Edward Gorey, "The Gashlycrumb Tinies"