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 bochecha, eric.araujo, eric.smith, pitrou, r.david.murray
Date 2010-08-13.13:49:44
SpamBayes Score 2.4621759e-06
Marked as misclassified No
Message-id <1281707382.3206.9.camel@localhost.localdomain>
In-reply-to <1281706051.38.0.744205755046.issue9584@psf.upfronthosting.co.za>
Content
> My view is that people using fnmatch/glob are expecting to get back
> the same list of files that they would if they ran 'echo
> <globpattern>' in the shell.

But it's not the case since we currently don't process braces anyway.

> The major shells (sh, bash, zsh, csh) seem to be pretty consistent in
> this regard (though sh does less brace expansion than the others...but
> is almost always actually bash these days).

Excluding the 95% (or so) of Windows users, I suppose.

> The special magic of fnmatch/glob is that it does a
> not-so-easy-to-get-right transformation of *shell* globbing rules into
> regular expressions behind the scenes.  That is, in my view its
> *purpose* is to be compatible with the "normal rules" for unix shell
> globbing.

I've never thought that the purpose of glob or fnmatch was to reproduce
shell rules. It's simply a convenient primitive. Wildcard expansion
exists in lots of other software than Unix shells.
History
Date User Action Args
2010-08-13 13:49:47pitrousetrecipients: + pitrou, eric.smith, eric.araujo, r.david.murray, bochecha
2010-08-13 13:49:45pitroulinkissue9584 messages
2010-08-13 13:49:44pitroucreate