Hey, you came back.

All right, lets build this appointment scheduler, thing.

If you need a reminder we're building a script that takes a date and time, and

then gives it back to us in six other time zones.

My idea for this is that you'd use it to figure out what time your meetings are in

other time zones for all of your intercontinental business meetings.

So we have two hard steps, turning our datetime into UTC.

And then making our six other datetimes.

I'll see you in workspaces.

I'm going to call this file meetings.py.

And first thing I want to do is I want to import datetime.

And actually, what I want to do is I just want the datetime

part of datetime, so I'm just going to do from datetime, import datetime.

I don't need timedeltas or any of that other stuff, I just need datetimes.

And then I'm gonna import pytz as well.

I also need to make the list of time zones that I want to convert my times into.

Now, I could use random and pick six random ones from pytz.all time zones.

That's fine, if that's what you wanna do, but I'm gonna go ahead and

[SOUND] just specify some.

So we're gonna make a list.

And in that list we're gonna have

pytz.timezone, U.S. Eastern,

Pacific Auckland, Asia Calcutta.

None of these should be super surprising.

UTC, which we could've got, again, done pytz.utc.

Try saying that a few times fast.

And then let's do Europe/Paris.

And let's do Africa/Khartoum.

All right.

If, in case, you're wondering how I know all these, I looked them up.

I didn't just memorize all of these time zones.

But I wanted to spread them out a little bit.

Kinda move them around the world some.

So that's why they're spread out like this.

So then let's, let's build our format string again.

[BLANK_AUDIO]

So holding onto seconds there is a little silly because I'm not going to

actually show seconds or even capture seconds from the user.

But we're just, we're using the string that we used before.

So that's why seconds are already there.

Now, let's make the actual meat of the script.

We don't have to do this in a continuous loop, if you didn't want to.

Maybe you wanted to be able to, you wanted the user to restart the script, or

you wanted to import this and use it somewhere else, whatever.

Maybe you'd write a function.

But I'm just gonna have it run forever, in case they give me a bad string and

they don't have to restart at that point.

So, we're going to do while true and

then inside of here, we need to get the date from the user.

Right?

So let's do a date input equals input,

when is your meeting, nope, not metting, meeting.

Please use MM DD YYYY HH MM format and

let's try local date equals

datetime.strptime, date input.

And we have to specify what our string is.

So, we're using two months, two days, and four years and then hours and minutes.

Except if they give me a bad one and I get a value error.

Then I want to print doesn't seem to be a valid date and time.

And then we put in there date input.

Right?

Okay.

But if that's all good then we're going to use our else.

This works much like the else in the for loops or in an if condition.

The try happens and that runs the code that might explode.

If it explodes, the accept happens.

If it doesn't explode.

The else happens.

Again, it's a little bit strangely named, but that's the way it works.

So the else is there for when our try does not blow up.

So let's override local date to be

pytz.timezone U.S. Pacific.

And use that to localize local date.

So we're just overwriting local date back into it, itself.

But we're going to turn it into a U.S.

Pacific timezone, because I'm in the U.S. Pacific timezone.

If you, for instance, are in U.S. Eastern or wherever,.

Change that string to match your local timezone.

And the UTC date is going to be local,

local date.as timezone pytz.timezone UTC.

Again, we could do here UTC and that would be perfectly fine.

What do we wanna do now?

Well, we want to generate this list of datetimes, right?

So we need a place to put that, so we'll hold onto a list here.

And then let's say for timezone in OTHER TIMEZONES, okay?

So for each of those other time zones.

Output.append utc date.as timezone,

whatever timezone we're currently on, yeah?

Okay, so that's good for that, and now for appointment in output.

For everything that's inside of output,

let's print appointment.strf time format.

And then we can do a break after that.

So that way our script does end,

it just doesn't end just because they gave us a bad date.

It ends once they've given us good dates, and we run through everything.

Okay, let's give it a test.

Come down here, python meeting.py.

Okay, when is my meeting?

Please use this.

Okay let's see.

It's going to be on May 16th,

2015 at 18:30.

[SOUND] Oh.

I misspelled appointment.

[SOUND] Gotta watch out for those spelling errors kids.

They will getcha every time.

[SOUND] All right.

So let's try this again.

5, 16, 2015, at 18:30.

All right so there we go.

So for Eastern Daylight Time that will be at, what is that, 9:30?

For Auckland it'll be the next day at 1:30 p.m.

For India it'll be 7:00 a.m.

For UTC it'll be at 1:30.

These are all the next day notice.

For let's see CEST would be Paris.

So for Paris it'll be at 3:30.

And for Khartoum over there in Egypt it'll be at 4:30.

So that's pretty cool.

We can, we can change all of our dates and times however we want.

There's definitely plenty more that can be done with this script.

We don't have a built in way to end the script early, and these are can't

pick the timezones they need to convert the submitted date time too.

Feel free to add both of those or other improvements and post them to the forum.

Be sure to tag me so I can see them.

Well, thanks for learning about date times and time zones with me.

It's not the most glamorous area of programing, or python, but

they are one of the more useful pieces.

And you'll definitely find yourself using them repeatedly.

I'll see ya next time.