On Feb 25, 2010, at 4:00 AM, Jannis Leidel wrote: > For the record, I'm generally +1 on this proposal and have used the concept > myself in a few projects outside of Pinax and enjoyed using it when working > with Transifex.
Carl and I discussed this in person and I'm +1 too. > It requires a little attention in case a project needs to be distributed > since the conf files are package data to distutils because if we don't add a > ``__init__.py`` to the ``conf/`` dir. A ``recursive-include > path/to/conf/*.ext`` in the manifest template of the project (if it exists) > suffices. I don't think we should add a __init__.py but should document the need for a recursive-include for packaging. > Regarding the file extension, I'm torn between using the ``.conf`` file > extension, which might be a source for confusion since it hides the fact that > "it's just Python", and ``.conf.py`` which is more verbose but would > highlight the fact that it's a non-importable config file and would still > conveniently apply Python code highlighting. .conf.py feels a little odd to me. My preferences is just .py but I do prefer .conf.py to just .conf (for the code highlighting) James -- You received this message because you are subscribed to the Google Groups "Pinax Core Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pinax-core-dev?hl=en.
