Diego Queiroz added the comment:
"I would agree if mkpath were a public function."
So It is better to define what a "public function" is. Any function in any
module of any project, if it is indented to be used by other modules, it is
public by definition.
If new pe
Diego Queiroz added the comment:
You were right, "os.makedirs" fits my needs. :-)
Anyway, I still think the change in the documentation is needed.
This is not an implementation detail, it is part of the way the function works.
The user should be aware of the behavior when he
Diego Queiroz added the comment:
Suppose the application creates one folder and add some data to it:
- /scratch/a/b/c
While the application is still running (it is not using the folder anymore),
you see the data, copy it to somewhere and delete everything manually using the
terminal.
After
Diego Queiroz added the comment:
Well. My application does not actually randomly remove the folders, it just
can't guarantee for a given process how the folder it created will be deleted.
I have many tasks running on a cluster using the same disk. Some tasks creates
the folders/file
New submission from Diego Queiroz :
There is a problem with dir_util cache (defined by "_path_created" global
variable).
It appears to be useful but it isn't, just repeat these steps to understand the
problem I'm facing:
1) Use mkpath to create any path (eg. /home/use
