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 pitrou
Recipients eli.bendersky, eric.araujo, giampaolo.rodola, ncoghlan, pitrou, ubershmekel
Date 2012-02-08.16:09:58
SpamBayes Score 1.1360302e-10
Marked as misclassified No
Message-id <1328717232.3387.20.camel@localhost.localdomain>
In-reply-to <CAF-Rda9m-JMvX-5K_kJawANh-rLL3+tTi81eP_zEzeL7jhFEKQ@mail.gmail.com>
Content
> Google "walk directory". First hit is a Rosetta code page with
> *recursive* walking implemented in various languages. So I guess it
> does have this connotation. Regardless, os.walk has been in Python for
> ages, and it's always been the go-to tool for recursive traversal.
> walkdir's name suggests the same.

You still haven't explained what your problem is with the idea of an
explicitly recursive glob (as both "rglob" and "globtree" suggest).

> walkdir is a new module proposal. If its API is tedious and awkward,
> it should probably be improved *now* while it's in development.

walkdir is not yet a module proposal, there's not even a PEP for it, and
it's in a very young state.

This issue has a working patch for rglob(), which is a single, obvious,
incremental addition to the existing glob module. If you want to discuss
walkdir, I suggest you do it in a separate issue.

(and, yes, rglob() can be reimplemented using walkdir later, if there is
a point in doing so)
History
Date User Action Args
2012-02-08 16:09:59pitrousetrecipients: + pitrou, ncoghlan, giampaolo.rodola, eric.araujo, eli.bendersky, ubershmekel
2012-02-08 16:09:59pitroulinkissue13968 messages
2012-02-08 16:09:58pitroucreate