Isnt there an i18n extension built on lib ICU in python , like Intl extension in PHP ? http://site.icu-project.org/ I'm sure there are better alternatives than just regexp to validate numbers, emails ,etc ...
Common Regular Expressions Made Simple
11–20 of 25 posts
Re: Common Regular Expressions Made Simple
#12I'm gonna be That Guy and say that the e-mail regex isn't upto scratch and probably should not be included. generally, very good.
Re: Common Regular Expressions Made Simple
#13I'm gonna be That Guy and say that the e-mail regex isn't upto scratch and probably should not be included. generally, very good.
I'm gonna be That Other Guy and say that the date and phone regex are respectively english-language and US specific. So it's common for a narrow definition of common.
> There is always a well-known solution to every human problem — neat, plausible, and wrong.
often paraphrased as "For every complex problem there is an answer that is clear, simple, and wrong."
Re: Common Regular Expressions Made Simple
#14Isnt there an i18n extension built on lib ICU in python , like Intl extension in PHP ? http://site.icu-project.org/ I'm sure there are better alternatives than just regexp to validate numbers, emails ,etc ...
It's not validation in this case, it's finding them in a body of text. For validation you generally have it easier because you often only deal with a single datum in a field (and thus string).
Of course further complexity is added in people being able to provide partial and context-dependent information, which is much harder to detect e.g. "December 3rd"
Re: Common Regular Expressions Made Simple
#15That project shows there are two tracks by which to tackle the problem that regex syntax is incoherent gobbledygook. The first is creating a regex version of pho with 5000 functions and mix and match names piece by piece. The second is to rename regex symbols to something that is easier for humans to parse.
Re: Common Regular Expressions Made Simple
#16Earlier quoted context omitted.
The time regex is, too. In German you can expect to encounter the text fragment > um 6:00 am 05.12. (at 6:00 on 12/05/..) If i read it correctly, the time regex would extract "6:00 am" as time, but the "am" is wrong (German uses 24h format).
"Um 12:30 am..." seems like a better example, since 6:00 is still 0600, but one parsing would make 12:30 am into 0030 rather than the intended 1230.
Re: Common Regular Expressions Made Simple
#17Earlier quoted context omitted.
The time regex is, too. In German you can expect to encounter the text fragment > um 6:00 am 05.12. (at 6:00 on 12/05/..) If i read it correctly, the time regex would extract "6:00 am" as time, but the "am" is wrong (German uses 24h format).
Haha that's excellent. Reminds me of a normalisation rule I wrote as part of a larger system to convert "Joe Bloggs Md." into "Dr. Joe Blogs MD" (where MD is Medical Doctor). TIL that "Md." is a common abbreviation for "Mohammed" in large parts of the world...
Re: Common Regular Expressions Made Simple
#18I'm gonna be That Guy and say that the e-mail regex isn't upto scratch and probably should not be included. generally, very good.
I'm the guy who says "poke the SMTP server" rather than validate the email address.
Re: Common Regular Expressions Made Simple
#19Earlier quoted context omitted.
I'm gonna be That Other Guy and say that the date and phone regex are respectively english-language and US specific. So it's common for a narrow definition of common.
I'm gonna be That Other Other Guy and say....stuff like this is the reason why most programmers I meet take ages to do anything custom. Evey body uses this framework and that library and make bulky code that could actually be implemented with 2 far more efficient lines and will struggle when the need to customize presents itself. Learn Regex...you will have a crazy powerful weapon in your arsenal.
This is an excellent point. Petty substitutions like verbal expressions might be useful if you're just getting started, but ultimately it's a crutch and it's best just to learn pure regular expressions. They're not that difficult.
Same with bundling a ton of dependencies. Lots of people (especially contemporary programmers, primarily web developers) seem to be deathly afraid of writing custom code to handle a job. It's not "reinventing the wheel", it's implementing logic easily extensible within your application without the hassle of upstream, especially if you're only using a small portion of a library or framework. Using 15 libraries for a 600-line script isn't best practice, it's cowardice.
Re: Common Regular Expressions Made Simple
#20Earlier quoted context omitted.
I'm gonna be That Other Other Guy and say....stuff like this is the reason why most programmers I meet take ages to do anything custom. Evey body uses this framework and that library and make bulky code that could actually be implemented with 2 far more efficient lines and will struggle when the need to customize presents itself. Learn Regex...you will have a crazy powerful weapon in your arsenal.
Why is this being downvoted? This is an excellent point. Petty substitutions like verbal expressions might be useful if you're just getting started, but ultimately it's a crutch and it's best just to learn pure regular expressions. They're not that difficult. Same with bundling a ton of dependencies. Lots of people (especially contemporary programmers, primarily web developers) seem to be deathly afraid of writing cu…