On Fri, May 11, 2018 at 11:36 AM, Gene Heskett <ghesk...@shentel.net> wrote: > So other than the *nix chmod, and some similar stuff in > os9/nitros9/amigados, I have never had to deal with octal. I'm sure the > security people would be pleased if another bit could be expanded into > the permissions that chmod controls, so lets deprecate octal and be done > with it.
What do you mean, "another bit"? Currently, the chmod command on my system can manage nine primary bits (rwx for each of ugo), plus setuid, setgid, and sticky. Plus there's a flag for "this is a symbolic link" and another for "this is a directory", and at least one or two for devices. > Computers haven't read a single 8 bit byte in years, some > reading 128 or 256 bits in a single read cycle today. Bring the language > into the 21st century. Remind me how you parse an IP packet (v4 or v6). Do you work with 256 bits at a time? And if you say "nobody parses network packets in Python", it's a lot more likely that you'll do network debugging in Python than that you'll care how exactly your CPU retrieves data from DRAM. Marking octal literals with "0o" was the right decision. Excising octal from the language would not be. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
