Hi all, thanks for your feedback in the "status update" thread. It is now clear to me that the "class" directive should be consistent in docutils and sphinx; and so we need a new name for "class".
First the easy thing, i.e. the transition: I think it would be good to introduce a config value "class_directive" that switches the class directive's meaning according to its value; it would default to the previous Sphinx behavior first, and then switch to defaulting to docutils' class. "cssclass" will be faded out. Now, finding a new name for "class" is hard. Looking at Python naming tradition, both "type" and "classobj" would be candidates. "klass" is also commonly used when a Python identifier is called for, but of these, only "classobj" would be possible I think. Other similar suggestions have been "concrete-class" (together with a new "abstract-class"), "sclass", "pclass", and "cls". There have been suggestions to move all code-documenting directives into a namespace of sorts, i.e. "code.class", "code.function" etc. This doesn't appeal to me very much; it sounds like a complication where none is needed, and doesn't lead to nice to read markup. It also has the disadvantage that *all* existing directives will have to go. Still, if enough people are in favor... In any case, I'd like to have some more people speak up about their preferences! cheers, Georg PS: My other suggestion of an extensions repository has only been given one +1, so I think I'll just create it and see :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" 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/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
