Timezone handling basics in Pandas - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to convert a naive datetime to UTC timezone.

Pandas

import pandas as pd
naive_dt = pd.Timestamp('2024-01-01 12:00:00')
aware_dt = naive_dt.tz_localize([1])
print(aware_dt)

Drag options to blanks, or click blank then click option'

A'UTC'

B'local'

C'GMT+5'

D'EST'

Attempts:

3 left

💡 Hint

Common Mistakes

Using tz_localize with a non-standard string like 'local' causes errors.

Confusing tz_localize with tz_convert.

Use tz_localize('UTC') to assign UTC timezone to a naive datetime.

2fill in blank

medium

Complete the code to convert a datetime from UTC to US/Eastern timezone.

Pandas

import pandas as pd
utc_dt = pd.Timestamp('2024-01-01 12:00:00', tz='UTC')
est_dt = utc_dt.tz_convert([1])
print(est_dt)

Drag options to blanks, or click blank then click option'

A'UTC'

B'Europe/London'

C'US/Eastern'

D'Asia/Tokyo'

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to tz_convert a naive datetime causes errors.

Using tz_localize instead of tz_convert on aware datetime.

Use tz_convert('US/Eastern') to convert from UTC to Eastern time.

3fill in blank

hard

Fix the error in the code to localize a naive datetime to 'Europe/London'.

Pandas

import pandas as pd
naive_dt = pd.Timestamp('2024-06-01 15:00:00')
aware_dt = naive_dt.[1]('Europe/London')
print(aware_dt)

Drag options to blanks, or click blank then click option'

Atz_convert

Btz_set

Ctz_change

Dtz_localize

Attempts:

3 left

💡 Hint

Common Mistakes

Using tz_convert on naive datetime causes AttributeError.

Using non-existent methods like tz_set or tz_change.

Use tz_localize to assign a timezone to a naive datetime.

4fill in blank

hard

Fill both blanks to create a dictionary of datetimes localized to UTC and converted to Asia/Tokyo.

Pandas

import pandas as pd
naive_dt = pd.Timestamp('2024-03-10 08:00:00')
localized = naive_dt.[1]('UTC')
tokyo_dt = localized.[2]('Asia/Tokyo')
result = {'UTC': localized, 'Tokyo': tokyo_dt}
print(result)

Drag options to blanks, or click blank then click option'

Atz_localize

Btz_convert

Attempts:

3 left

💡 Hint

Common Mistakes

Using tz_convert on naive datetime causes errors.

Swapping the order of localization and conversion.

First, localize naive datetime to UTC using tz_localize. Then convert to Tokyo timezone with tz_convert.

5fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps timezone names to converted datetimes if the name length is greater than 5.

Pandas

import pandas as pd
naive_dt = pd.Timestamp('2024-01-01 12:00:00')
tz_names = ['UTC', 'US/Eastern', 'Europe/London', 'Asia/Tokyo']
localized = naive_dt.tz_localize('UTC')
dt_dict = {name: localized.tz_convert(name) for name in tz_names if len(name) [1] [2] }
print(dt_dict)

Drag options to blanks, or click blank then click option'

A>

B5

C<

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' or '==' instead of '>' causes wrong filtering.

Incorrect operator or value in the condition.

The dictionary comprehension filters timezone names with length greater than 5 using len(name) > 5 and converts UTC datetime to each selected timezone.

Practice

1. What does the tz_localize method do in pandas when working with timestamps?

easy

A. Converts timestamps from one timezone to another.

B. Adds timezone information to timestamps without any timezone (naive timestamps).

C. Removes timezone information from timestamps.

D. Changes the timestamp format to string.

Solution

1. Step 1: Understand naive timestamps

   Naive timestamps have no timezone information attached.

2. Step 2: Role of tz_localize

   This method adds timezone info to naive timestamps without changing the actual time.

3. Final Answer:

   Adds timezone information to timestamps without any timezone (naive timestamps). -> Option B

4. Quick Check:

   tz_localize adds timezone [OK]

Hint: Remember: localize adds timezone, convert changes it [OK]

Common Mistakes:

• Confusing tz_localize with tz_convert
• Thinking tz_localize changes the time value
• Assuming tz_localize removes timezone info

2. Which of the following is the correct way to convert a timezone-aware pandas datetime Series dt from UTC to US/Eastern timezone?

easy

A. dt.tz_convert('US/Eastern')

B. dt.tz_localize('UTC').tz_convert('US/Eastern')

C. dt.tz_localize('US/Eastern')

D. dt.tz_convert('UTC')

Solution

1. Step 1: Check if dt is timezone-aware

   Since dt is timezone-aware, we use tz_convert to change its timezone.

2. Step 2: Apply correct method

   tz_convert('US/Eastern') converts from current timezone (UTC) to US/Eastern.

3. Final Answer:

   dt.tz_convert('US/Eastern') -> Option A

4. Quick Check:

   Convert aware timestamps with tz_convert [OK]

Hint: Use tz_convert only on timezone-aware timestamps [OK]

Common Mistakes:

• Using tz_localize on already aware timestamps
• Not converting timezone properly
• Confusing order of localization and conversion

3. Given the following code, what will be the output?

import pandas as pd
rng = pd.date_range('2024-01-01 12:00', periods=2, freq='H')
rng_utc = rng.tz_localize('UTC')
rng_est = rng_utc.tz_convert('US/Eastern')
print(rng_est)

medium

A. DatetimeIndex with times 17:00 and 18:00 in US/Eastern timezone

B. DatetimeIndex with times 12:00 and 13:00 in US/Eastern timezone

C. DatetimeIndex with times 07:00 and 08:00 in US/Eastern timezone

D. Error because tz_convert cannot be used after tz_localize

Solution

1. Step 1: Localize naive timestamps to UTC

   The original times are 12:00 and 13:00 UTC after tz_localize('UTC').

2. Step 2: Convert UTC times to US/Eastern timezone

   US/Eastern is UTC-5 in winter, so times become 07:00 and 08:00 with timezone info.

3. Final Answer:

   DatetimeIndex with times 07:00 and 08:00 in US/Eastern timezone -> Option C

4. Quick Check:

   UTC 12:00 -> EST 07:00 [OK]

Hint: Convert UTC to EST subtracts 5 hours [OK]

Common Mistakes:

• Assuming times stay the same after conversion
• Mixing up tz_localize and tz_convert order
• Expecting error instead of valid output

4. What is wrong with this code snippet?

import pandas as pd
dt = pd.to_datetime(['2024-01-01 10:00', '2024-01-01 11:00'])
dt = dt.tz_convert('Europe/London')

medium

A. Cannot use tz_convert on naive timestamps; must localize first.

B. The timezone string 'Europe/London' is invalid.

C. The to_datetime function needs a timezone argument.

D. The code is correct and runs without error.

Solution

1. Step 1: Check timestamp awareness

   The timestamps created by to_datetime are naive (no timezone).

2. Step 2: Understand tz_convert usage

   tz_convert requires timestamps to be timezone-aware; naive timestamps must use tz_localize first.

3. Final Answer:

   Cannot use tz_convert on naive timestamps; must localize first. -> Option A

4. Quick Check:

   tz_convert needs aware timestamps [OK]

Hint: Localize before convert on naive timestamps [OK]

Common Mistakes:

• Trying to convert timezone without localizing
• Assuming to_datetime adds timezone automatically
• Confusing error cause with invalid timezone string

5. You have a pandas Series of timestamps without timezone info representing local times in New York. You want to convert them to UTC timestamps correctly considering daylight saving time. Which sequence of operations should you perform?

hard

A. Convert timestamps to string first, then parse with UTC timezone.

B. Use tz_convert('UTC') directly on naive timestamps.

C. Use tz_localize('UTC') then tz_convert('America/New_York').

D. Use tz_localize('America/New_York') then tz_convert('UTC').

Solution

1. Step 1: Localize naive timestamps to New York timezone

   Since timestamps are local New York times without timezone, use tz_localize('America/New_York') to mark them as such, correctly handling daylight saving.

2. Step 2: Convert localized timestamps to UTC

   Use tz_convert('UTC') to get equivalent UTC times.

3. Final Answer:

   Use tz_localize('America/New_York') then tz_convert('UTC'). -> Option D

4. Quick Check:

   Localize then convert for correct timezone shifts [OK]

Hint: Localize first, then convert to UTC [OK]

Common Mistakes:

• Converting naive timestamps directly
• Localizing to wrong timezone first
• Ignoring daylight saving time effects