On Thu, Apr 24, 2014 at 2:18 AM, Chris Withers <ch...@simplistix.co.uk> wrote: > What were the compelling reasons to go from mixedCase to > underscore_separated? What's considered the best approach for migrating from > the former to the latter?
I never recall Python "going from" camelCase to separate_words. The descriptions of best practice you see in the PEP were always that way, as I recall. If you have a code base that does it some other way, I would leave it be. The primary hunk of code I work with is full of Boost.Python-generated bindings for C++ libraries, so leaks C++ naming style out of all its pores. A lot of the other pure Python code in this code base was written by people who were mostly C++ programmers, and didn't know PEP 8 from a hole in the ground. Consequently, the whole thing is riddled with all sorts of non-pep8-ness. I used to want to change everything, but just let that sleeping dog lie. I have better things to do with my life. New stuff I write tends to be much more pep8-ish. Skip _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
