This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author patrick.vrijlandt
Recipients docs@python, patrick.vrijlandt, pitrou, rosslagerwall, zbysz
Date 2012-01-16.15:56:26
SpamBayes Score 1.3749601e-06
Marked as misclassified No
Message-id <1326729387.1.0.786726344314.issue13779@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation of this function is generally ambiguous, because os.walk is a generator. Thus "generate" means (1) yielded from a generator and (2) prepared for later use within the generator. To avoid the ambiguity, "generate" should be avoided if possible. (1) might be replaced by "return" and (2) by "prepare".

@zbysz
The paragraph you cite is about "Modifying dirnames ". If you are not "Modifying dirnames" (like me) this section easily skips your attention.

My problem was, of course, that I had myself changed the directory structure - It's not a race condition with another process but an effect  of the loop os.walk was managing.

@pitrou
shutil.rmtree cannot help me, because I'm only deleting empty dirs.

Proposal (very verbose I'm afraid):
If you change the directory structure below dirpath while topdown=True, you can modify dirnames in-place so that walk will visit the right directories. If you change the directory structure below dirpath while topdown=False (maybe while you where there), dirnames and filenames can still reflect the old situation and it might be necessary to call os.listdir again.
History
Date User Action Args
2012-01-16 15:56:27patrick.vrijlandtsetrecipients: + patrick.vrijlandt, pitrou, zbysz, docs@python, rosslagerwall
2012-01-16 15:56:27patrick.vrijlandtsetmessageid: <1326729387.1.0.786726344314.issue13779@psf.upfronthosting.co.za>
2012-01-16 15:56:26patrick.vrijlandtlinkissue13779 messages
2012-01-16 15:56:26patrick.vrijlandtcreate