Homework 6: Regular Expressions




Rate this product

# Homework 6: Regular Expressions

The length of this homework is inversely proportional to your knowledge in writing regular expressions, both for finding matches and for doing substitutions.

## Background

Please refresh your memory of regular expressions using the class notes. You may also find the Python [documentation on regular expressions]( useful.

A few helpful reminders:

### Testing for Patterns

When you use `` to find a regular expression match, it returns a `Match` object if the pattern exists in the string (we will see more about objects later in the semester). If *there is no match*, then `` (and `re.match` and `re.findall`) will return `None`,  which you can test for:

p = re.compile(‘pattern’)
if ( :
# This branch will execute if the pattern is found
else :
# this branch will execute if the pattern is *not* found

### Substituting with functions

A common use of `re.sub` is to substitute one string for another (remember that you can use the *groups* that you match in a pattern as part of your string substitution):

s = “loooool”
p = re.compile(‘(l)o+(l)’)
p.sub(r’\1o\2′, s) #replace “loooool” with “lol”

You can also call a method instead of providing a replacement string. This method will be called with the `Match` object corresponding to the matched string, and should return a string:

def replFun(m) :
s = “loooool”
p = re.compile(‘(l)(o+)(l)’)
p.sub(r’\1’+replFun(m) +r’\3′, s) #replace “loooool” with “lOOOOOl”

# Instructions

## 0) Set up your repository

Click the link on Piazza to set up your repository for HW 6, then clone it.

The repository should contain three files:

1. ``, the file in which you will fill in the functions for the problems. This also contains test code you can use to test your solutions.
2. ``, contains a non-exhaustive set of test cases beyond what is provided in ``. You can use this file to test your work
3. This README.

## Problem 1: Regular expression matches

Fill in the function `problem1`. This function should return `True` if the input string *is a valid US/ Mexican phone number* and `False` if not. We define a valid phone number (belonging to either US/Mexico) as follows:

1. It begins with an *optional* country code. For the US the country code is **+1** and for Mexico the country code is **+52**.
2. A number that begins with a country code must have an area code (3 digits) and 7 digits following the area code.
3. A number without the optional country code is valid **iff** (if and only if) it does not include the 3 digit area code either and only has 7 digits.


*ANY other format should not count as a valid phone number. Spaces before or after an otherwise valid number is considered invalid.*

Remember that `(`, `)`, `-` and `.` are special characters for regular expressions. To search for those characters, you need to precede them with a backslash: `\(` `\)`, `\-`, `\.`.

Because we are looking for the entire string to be a phone number, you can either use `^` and `$` to force a match to be at the beginning and end of a string, or you can use `fullmatch` instead of `match` or `search`.

## Problem 2: Groups

Consider a regular expression that identifies street addresses and uses  the following format:

1. **One or more digits**, followed by a space.
2. **One or more words**, each **starting with a capital letter** and then **followed by zero or more lowercase letters**. This will be followed by a space.
3. A road type, **one of “Rd.”, “Dr.”, “Ave.” or “St.”**

So the following are valid street names:

`465 Northwestern Ave.`

`201 South First St.`

`22 What A Wonderful Ave.`

`333 This Through Rd.`

Assume that we will only test with valid door number and  street names. There will only be ‘one door number and one valid street name’ in a test case. However, there may be other words preceding or following the valid door number and street name. Please note the last test case and strictly adhere to the specifications in the address format mentioned above.

*We consider door numbers and street names to be valid if they satify the above mentioned rubric in problem 2. Hint: Using \w or \W will not solve this problem.*

Fill in the function `problem2`. This function should search an input string for any valid street address, then return *just the door number and street name* from that address: not the road type. So if you pass in:

`The EE building is at 465 Northwestern Ave.`

you should return:

`465 Northwestern`

If you pass in:

`Meet me at 201 South First St. at noon`

you should return:

`201 South First`

Also, if you pass in:

`123 Mayb3 Y0u 222 Did not th1nk 333 This Through Rd. Did Y0u Ave.`

you should return:

`333 This Through`.

*(Note: Existence of any character which interferes with any upper case letter, and the upper case letter may follow by zero or more lowercase letters.
After one or more digits invalidates the address name. This should indicate that you begin looking in the rest of the input)*

**Be careful not to return extra spaces in the return value. You may need to do a little bit of extra processing of the string captured by your group to ensure this. You will receive partial credit for having spaces. Please remove extra spaces for full credit.**

## Problem 3: Substitution

Fill in the function `problem3`. This function should *garble* addresses by returning the original address but with the street name reversed. For some of the above  examples, you should return:

`The EE building is at 465 nretsewhtroN Ave.`

`Meet me at 201 tsriF htuoS St. at noon`

*(Note that the entire street name is reversed, not word by word)*

and, if your input is `Go West on 999 West St.`,
you should return:

`Go West on 999 tseW St.`

*(Note that **only** the street name is reversed)*.

Two hints:

1. Think about creating three groups in your regular expression. One that captures the street number, one that captures the street name, and one that captures the road type. You can then use those three groups to assemble the desired output with garbled street name.
2. If you have a string `s`, `s[::-1]` is the reversed string.

You should feel free to write helper functions to help solve this problem.

**Be careful not to return extra spaces in the final output. You may need to do a little bit of extra processing of the string captured by your group to ensure this. You will receive partial credit for having unwanted spaces. Please remove extra spaces for full credit.**

# Testing Your Code

In `` we’ve provided a non-exhaustive series of test cases you can check your work with. Passing these tests doesn’t guarantee you full credit but failing them would certainly indicate a problem with your solutions. To run the tests, run the `` script in this directory.

# What to Submit

Please submit `` with all the functions filled in. You do not need to remove ``. However, your work will **only** be evaluated based on your submission of ``.

# Submitting your code

Please add, commit and push the latest version of your code, as you did in the previous HW.
Do not make any modifications to this post submission and prevent the late penalty.