text stringlengths 1 81 | start float64 0 10.1k | duration float64 0 24.9 |
|---|---|---|
quotation or double quotation because | 4,755.48 | 4.92 |
after the print we use a single | 4,757.659 | 5.681 |
quotation to represent the key of the | 4,760.4 | 6.12 |
dictionary but after the | 4,763.34 | 5.399 |
reading or writing we use the double | 4,766.52 | 3.9 |
quotation | 4,768.739 | 4.321 |
it's a good question in Python you can | 4,770.42 | 5.1 |
generally use double quotes or you can | 4,773.06 | 4.02 |
use single quotes and it doesn't matter | 4,775.52 | 3.78 |
you should just be self-consistent so | 4,777.08 | 4.139 |
that stylistically your code looks the | 4,779.3 | 4.5 |
same all throughout sometimes though it | 4,781.219 | 4.921 |
is necessary to alternate if you're | 4,783.8 | 4.08 |
already using double quotes as I was | 4,786.14 | 4.32 |
earlier for a long F string but inside | 4,787.88 | 5.04 |
that F string I was interpolating the | 4,790.46 | 4.199 |
values of some variables using curly | 4,792.92 | 3.9 |
braces and those variables were | 4,794.659 | 5.161 |
dictionaries and in order to index into | 4,796.82 | 5.82 |
a dictionary you use square brackets and | 4,799.82 | 4.44 |
then quotes but if you're already using | 4,802.64 | 3.36 |
double quotes out here you should | 4,804.26 | 4.439 |
generally use single quotes here or vice | 4,806 | 5.4 |
versa but otherwise I'm in the habit of | 4,808.699 | 4.261 |
using double quotes everywhere others | 4,811.4 | 2.94 |
are in the habit of using single quotes | 4,812.96 | 3.779 |
everywhere it only matters sometimes if | 4,814.34 | 6.24 |
one might be confused for the other | 4,816.739 | 6.601 |
other questions on dictionary uh writing | 4,820.58 | 5.579 |
or reading uh yeah I did my question is | 4,823.34 | 6.48 |
can we use multiple CSV files in any | 4,826.159 | 4.861 |
program | 4,829.82 | 3.48 |
absolutely you can use as many CSV files | 4,831.02 | 3.719 |
as you want and it's just one of the | 4,833.3 | 3.78 |
formats that you can use to save data | 4,834.739 | 5.541 |
other questions on csvs or file IO | 4,837.08 | 6.599 |
thanks for taking my question uh so when | 4,840.28 | 6.1 |
you're reading from the file the um you | 4,843.679 | 6.781 |
had the um as a dictionary you had the | 4,846.38 | 5.7 |
fields called | 4,850.46 | 2.94 |
um couldn't you just call it when you're | 4,852.08 | 2.579 |
reading could couldn't you just call the | 4,853.4 | 3.06 |
row in the previous version of the of | 4,854.659 | 5.401 |
the students uh Pi file | 4,856.46 | 6.719 |
um when you're reading the uh when | 4,860.06 | 4.2 |
you're reading each row you are | 4,863.179 | 6.261 |
splitting out the um the fields by name | 4,864.26 | 5.18 |
yeah so when you're appending to the uh | 4,870.26 | 4.2 |
to the students list can you just call | 4,872.239 | 4.201 |
the uh for row and reader | 4,874.46 | 4.86 |
students.append row rather than | 4,876.44 | 5.46 |
uh rather than naming each of the fields | 4,879.32 | 5.96 |
oh very clever uh short answer yes | 4,881.9 | 7.5 |
insofar as dick to reader returns one | 4,885.28 | 6.879 |
dictionary at a time when you Loop over | 4,889.4 | 4.62 |
it rho is already going to be a | 4,892.159 | 4.5 |
dictionary so yes you could actually get | 4,894.02 | 4.5 |
away with doing this and the effect | 4,896.659 | 4.56 |
would really be the same in this case | 4,898.52 | 4.98 |
good observation how about one more | 4,901.219 | 4.801 |
question on csvs | 4,903.5 | 6.48 |
yeah when reading in csvs from my past | 4,906.02 | 6.84 |
work with data a lot of things can go | 4,909.98 | 4.62 |
wrong I don't know if it's a fair | 4,912.86 | 3.48 |
question that you can answer in a few | 4,914.6 | 3.96 |
sentences but are there any best | 4,916.34 | 6.299 |
practices to double check that sort of | 4,918.56 | 7.02 |
no mistakes occurred it's a really good | 4,922.639 | 5.221 |
question and I would say in general if | 4,925.58 | 5.099 |
you're using code to generate the csvs | 4,927.86 | 5.7 |
and to read the csvs and you're using a | 4,930.679 | 4.5 |
good Library theoretically nothing | 4,933.56 | 4.38 |
should go wrong it should be 100 correct | 4,935.179 | 6.361 |
if the libraries are 100 correct you and | 4,937.94 | 5.279 |
I tend to be the problem like when you | 4,941.54 | 4.679 |
let a human touch the CSV or when Excel | 4,943.219 | 4.681 |
or apple numbers or some other tools | 4,946.219 | 3.601 |
involved that might not be aligned with | 4,947.9 | 3.96 |
your code's expectations things then yes | 4,949.82 | 5.46 |
can break the goal really sometimes | 4,951.86 | 5.22 |
honestly the solution is manual fixes | 4,955.28 | 4.379 |
you go in and fix the CSV or you have a | 4,957.08 | 4.2 |
lot of error checking or you have a lot | 4,959.659 | 3.901 |
of try except just to tolerate mistakes | 4,961.28 | 4.56 |
in the data but generally I would say if | 4,963.56 | 4.32 |
you're using CSV or any file format | 4,965.84 | 4.56 |
internally to a program to both read and | 4,967.88 | 4.38 |
write it you shouldn't have concerns | 4,970.4 | 3.66 |
there you and I the humans are the | 4,972.26 | 3.84 |
problem uh generally speaking and not | 4,974.06 | 4.079 |
the programmers the users of those files | 4,976.1 | 4.32 |
instead all right allow me to propose | 4,978.139 | 4.741 |
that we leave csvs behind but to note | 4,980.42 | 4.02 |
that they're not the only file format | 4,982.88 | 3.9 |
you you can use in order to read or | 4,984.44 | 3.9 |
write data in fact they're a popular | 4,986.78 | 4.379 |
format as is just raw text files dot txt | 4,988.34 | 5.1 |
files but you can store data really any | 4,991.159 | 4.381 |
way that you want we've just picked csvs | 4,993.44 | 3.779 |
because it's representative of how you | 4,995.54 | 3.659 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.