On Wed, May 18, 2011 at 21:33, anatoly techtonik <techto...@gmail.com>wrote:
> On Wed, May 18, 2011 at 3:47 PM, Brian Curtin <brian.cur...@gmail.com> > wrote: > > > > On May 18, 2011 7:03 AM, "anatoly techtonik" <techto...@gmail.com> > wrote: > >> > >> Greetings, > >> > >> While studying `virtualenv` code I've noticed that in Python directory > >> tree `include`, `libs` and `tcl` are lowercased while other dirs are > >> capitalized. It doesn't seem important (especially for developers > >> here), but it still can leave an unpleasant image for people new to > >> Python (and programming in general). > > > > In theory there are probably a lot of things that might seem unpleasant > but > > are actually non-issues. I don't believe there have been any complaints > > about actual unpleasantries with directory case. > > Among web folks there are no people who care less about typography > than those who spend most of their time in text terminals. =) I think > that probability of receiving such complaint is very low even if > everybody notices that. "Why should I bother about consistency if > Python developers are not giving damn about it?" > > >> > >> ├[Python27] > >> │ ├─DLLs > >> │ ├─Doc > >> │ ├─include > >> │ ├─Lib > >> │ ├─libs > >> │ ├─Scripts > >> │ ├─tcl > >> │ └─Tools > >> > >> How about making a consistent lowercased or uppercased scheme? Windows > >> filesystems are case-insensitive, so the change shouldn't affect > >> anybody. > > > > Some Macs have case-sensitive file systems, and some people use > > case-sensitive file systems on various flavors of UNIX. The change would > > probably require a thorough look through the build chain. > > But we are speaking only about Windows. > Definitely -1 to change the folder names only on Windows.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com