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 josh.r
Recipients cykerway, josh.r, serhiy.storchaka, xtreak
Date 2018-11-26.23:10:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1543273836.22.0.788709270274.issue35314@psf.upfronthosting.co.za>
In-reply-to
Content
Finished typing this while Serhiy was closing, but just for further explanation:

This isn't a bug. fnmatch provides "shell-style" wildcards, but that doesn't mean it supports every shell's extensions to the globbing syntax. It doesn't even claim support for full POSIX globbing syntax. The docs explicitly specify support for only four forms:

*
?
[seq]
[!seq]

There is no support for [^seq]; [^seq] isn't even part of POSIX globbing per glob(7):

"POSIX has declared the effect of a wildcard pattern "[^...]" to be undefined."
History
Date User Action Args
2018-11-26 23:10:36josh.rsetrecipients: + josh.r, serhiy.storchaka, cykerway, xtreak
2018-11-26 23:10:36josh.rsetmessageid: <1543273836.22.0.788709270274.issue35314@psf.upfronthosting.co.za>
2018-11-26 23:10:36josh.rlinkissue35314 messages
2018-11-26 23:10:36josh.rcreate