guy keren wrote: >regarding input() vs. raw_input() - firefox shows me your text quite >confused - so i didn't understand what you favor - input() or raw_input(). > > He was actually saying that (for simple programs) there are opposing oppinions. My personal vote: raw_input . Reasons: 1) For bigger programs there's general agreement that input() is bad, so we'd better avoid teaching bad habits from the start. 2) Zen of python - explicit is better than implicit. You want anything other than string? Say exactly what you want. 3) '2' is not 2 . Avoid hiding the issue of types. It's an important concept, and handwaving your way around it would become a major source of confusion in later lessons.
- Re: updated python material - start of python refere... Shlomi Fish
- Re: updated python material - start of python re... Amit Aronovitch
- Re: updated python material - start of pytho... Shlomi Fish
- Re: updated python material - start of python refere... Nir Soffer
- Re: updated python material - start of python re... Amit Aronovitch
- Re: updated python material - start of pytho... Nir Soffer
- Re: updated python material - start of p... Amit Aronovitch
- Re: updated python material - start... guy keren
- Re: python reference Beni Cherniavsky
- Re: python reference guy keren
- Re: python reference Amit Aronovitch
- Re: updated python material - start of python reference Amit Aronovitch
- Re: updated python material - start of python refere... guy keren
- Re: updated python material - start of python re... Amit Aronovitch
- Re: updated python material - start of python refere... Beni Cherniavsky
