[ and ] can be used as regular filename characters (at least on Linux). And yet, isfname does not include these by default.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Well, I'd say [ and ] are extremely unlikely characters to be find in filenames on Unix. except for /usr/bin/[ I am not aware of any such characters actually in use. I don't think changing the default for those characters makes sense, but that does not mean, you cannot tweak that default to your liking.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
are extremely unlikely characters to be find in filenames on Unix.
On the contrary, it's rather common within web frameworks, to denote parametrized routes. Example.
you cannot tweak that default to your liking.
That's what I ended up doing (for the time being), but due to the prevalence of such web frameworks, I think there's an argument to be made that this should be the default.
Sorry if initial comment wasn't clear that this is, in fact, a lot more common than it seems!
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()