[Zope-dev] Proposal: zope.app.publisher refactoring

Martijn Faassen faassen at startifact.com
Tue Aug 25 12:46:02 EDT 2009


Dan Korostelev wrote:
> 2009/8/24 Stephan Richter <srichter at cosmos.phy.tufts.edu>:
>> On Friday 21 August 2009, Dan Korostelev wrote:
>>> BrowserSkinsVocabulary - this can be moved to zope.publisher.browser
>>> and rewritten with zope.schema's SimpleVocabulary not to introduce
>>> dependency on zope.componentvocabulary.
>> -1. Why? The reason we wrote the zope.componentvocabulary code originally was
>> exactly to avoid the constant reimplementation of that code.
> 
> Well, the only reason is that zope.publisher currently doesn't depend
> on zope.componentvocabulary. But it doesn't matter for me personally,
> so if steering group decides that it's okay to add a dependency on
> zope.componentvocabulary to zope.publisher, I won't rewrite the
> vocabulary with SimpleVocabulary :-)

For the reasons of code stability let's rely on zope.componentvocabulary 
then, at least for now. zope.componentvocabulary doesn't look like it 
adds serious dependencies.

Regards,

Martijn




More information about the Zope-Dev mailing list