Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #103369 > unrolled thread
| Started by | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| First post | 2016-02-22 14:51 -0800 |
| Last post | 2016-02-22 14:51 -0800 |
| 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: Make a unique filesystem path, without creating the file Ethan Furman <ethan@stoneleaf.us> - 2016-02-22 14:51 -0800
| From | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| Date | 2016-02-22 14:51 -0800 |
| Subject | Re: Make a unique filesystem path, without creating the file |
| Message-ID | <mailman.52.1456181443.20994.python-list@python.org> |
On 02/22/2016 02:25 PM, Cameron Simpson wrote: > On 22Feb2016 10:11, Ethan Furman <ethan@stoneleaf.us> wrote: >> On 02/14/2016 04:08 PM, Ben Finney wrote: >> >>> I am unconcerned with whether there is a real filesystem entry of that >>> name; the goal entails having no filesystem activity for this. I want a >>> valid unique filesystem path, without touching the filesystem. >> >> This is impossible. If you don't touch the file system you have no >> way to know if the path is unique. > > I think Ben wants to avoid filesystem modification (let us ignore atime > here). So one can read the filesystem to see what is current, but he > does not want to actually make any new filesystem entry. Hmm -- well, he says "the goal entails having no filesystem activity for this", and seeing what already exists definitely requires file system activity . . . -- ~Ethan~
Back to top | Article view | comp.lang.python
csiph-web