Agreed. Between "don't duplicate" and "don't obfuscate," I think "don't obfuscate" wins this round. There was a similar situation with ``_define_paths``, but in this case the duplicated code is shared by two classes, so it would have to sit "far away" in the module. I'm open to be swayed though....