1
00:00:08,482 --> 00:00:12,385
Welcome back for a few tips on file names.

2
00:00:12,385 --> 00:00:16,716
Some older computer operating systems
place a lot of restrictions on file names,

3
00:00:16,716 --> 00:00:20,484
for example, early versions of
Windows only allowed eight characters

4
00:00:20,484 --> 00:00:22,950
before the period and
three after the period.

5
00:00:24,020 --> 00:00:28,058
Modern computer operating systems have
fewer restrictions on your file names.

6
00:00:28,058 --> 00:00:32,118
Still, it's a good idea for
maximum portability of your files between

7
00:00:32,118 --> 00:00:35,107
computers to place a few
restrictions on yourself.

8
00:00:36,150 --> 00:00:37,680
Here are our suggestions.

9
00:00:37,680 --> 00:00:41,904
First of all,
don't use commas in a file name.

10
00:00:41,904 --> 00:00:45,420
So don't say, Olympics, winter.

11
00:00:47,670 --> 00:00:51,630
Don't make that be a file name even if
your computer operating system allows it.

12
00:00:53,200 --> 00:00:59,015
Don't use more than one
period like .txt.3.csv.

13
00:00:59,015 --> 00:01:00,492
Don't do that.

14
00:01:00,492 --> 00:01:04,848
Don't use a forward slash or
a backward slash in your file name.

15
00:01:04,848 --> 00:01:07,855
No Olympic/winter.

16
00:01:07,855 --> 00:01:11,257
That's usually the convention for
making subdirectories.

17
00:01:11,257 --> 00:01:14,997
You don't want to have
a slash in your file name or

18
00:01:14,997 --> 00:01:17,437
a backslash in your file name.

19
00:01:17,437 --> 00:01:21,404
Don't use spaces even though most
operating systems will permit that now.

20
00:01:21,404 --> 00:01:27,446
Olympic space winter,
also not a good idea.

21
00:01:27,446 --> 00:01:32,801
Do follow some conventions for
what happens after the period.

22
00:01:32,801 --> 00:01:37,161
.txt should be for plain text.

23
00:01:37,161 --> 00:01:41,198
.py, if you've got a file
that's Python code.

24
00:01:42,861 --> 00:01:49,547
.csv, if you've got text that's in
the comma separated values format.

25
00:01:49,547 --> 00:01:55,324
So we've actually been bad here,
we've got this file olympics.txt,

26
00:01:55,324 --> 00:01:58,837
it really should have been olympics.csv.

27
00:01:58,837 --> 00:02:02,536
Another file ending is .xls.

28
00:02:02,536 --> 00:02:08,140
That's for files that are in
a Microsoft Excel format.

29
00:02:08,140 --> 00:02:13,232
.doc or .docx for
things that are in Microsoft Word format.

30
00:02:13,232 --> 00:02:18,490
The reason for following these conventions
about what goes after the period,

31
00:02:18,490 --> 00:02:23,431
is that computer operating systems
will usually look at that extension,

32
00:02:23,431 --> 00:02:25,915
the .txt or the .csv, or the .py.

33
00:02:25,915 --> 00:02:29,959
If you just double click on the file
they'll decide which program to open.

34
00:02:29,959 --> 00:02:33,575
So if it's a .py file they'll try
to open it in a text editor or

35
00:02:33,575 --> 00:02:36,373
they'll try to execute
it as a Python program.

36
00:02:36,373 --> 00:02:41,695
If you have a .xls, it'll try to open
it in Microsoft Excel and so on.

37
00:02:41,695 --> 00:02:46,363
So that's all for now, just a few words
on naming conventions for your files.

38
00:02:46,363 --> 00:02:47,520
I'll see you next time.