Open GoogleCodeExporter opened 8 years ago
Thanks for reporting this issue.
I reason why I didn't support symbolic linking is because it might be
dangerous. It is very easy to loop yourself and python will not prevent this.
But I understand why you want this feature. In the upcoming version I will,
support multiple paths and I add and options to allow symbolic links (which
will be disabled by default, but if you want you can enable it).
Expect a new release around the end of the month
Original comment by romke.va...@gmail.com
on 22 Apr 2012 at 7:48
Btw, python2.5 doesn't support symboliclinks. Need to create some workaround
for this:
http://docs.python.org/library/os.html#os.walk
Original comment by romke.va...@gmail.com
on 22 Apr 2012 at 7:51
Original comment by romke.va...@gmail.com
on 22 Apr 2012 at 8:39
Labels: -Type-Defect Type-Enhancement OpSys-Linux OpSys-OSX
Windows also has symlink support, you might want make sure that it also works
for your Windows users.
mklink [[/d] | [/h] | [/j]] <Link> <Target>
Original comment by Donny.va...@gmail.com
on 22 Apr 2012 at 2:22
Original comment by romke.va...@gmail.com
on 23 Apr 2012 at 11:38
Btw, thanks donny didn't know that.
I have been playing around with the os.walk function. Because we want to
support python version 2.5 a workaround is needed for symbolic links. I based
my workaround on the code used in version 2.6 for this feature.
def walkdir(path):
for dirname, dirnames, filenames in os.walk(path):
for dirname2 in dirnames:
if os.path.islink(os.path.join(path,dirname2)):
walkdir(dirname2)
Original comment by romke.va...@gmail.com
on 23 Apr 2012 at 12:28
Original comment by romke.va...@gmail.com
on 18 May 2012 at 12:01
Original comment by romke.va...@gmail.com
on 21 May 2012 at 1:52
Original comment by romke.va...@gmail.com
on 8 Nov 2012 at 5:45
Original comment by romke.va...@gmail.com
on 19 Apr 2013 at 5:16
Original comment by romke.va...@gmail.com
on 20 Jun 2013 at 1:01
Original issue reported on code.google.com by
h...@wevers.org
on 21 Apr 2012 at 9:06