When using configs of dist.plone.org I often get the error cited below, which derives of the referenced config zopetoolkit-1-0-8-ztk-versions.cfg, pinning mechanize to a very old version, which in return conflicts with the requirement of zope.testbrowser, demanding a higher version of mechanize.
While resolving this would be nice (unpinning leads to another error) the question comes up, if zope.testbrowser needs to be involved in a non-testing environment at all?
And even more importantly: Can the configs of dist.plone.org be seen as a reliable source or is it better to use other sources?
version and requirements information containing mechanize: [versions] constraint on mechanize: 0.1.11 Requirement of zope.testbrowser: mechanize>=0.2.0 While: Installing. Getting section instance. Initializing section instance. Installing recipe plone.recipe.zope2instance. Error: The requirement ('mechanize>=0.2.0') is not allowed by your [versions] constraint (0.1.11)
When using configs of dist.plone.org I often get the error cited below, which derives of the referenced config
zopetoolkit-1-0-8-ztk-versions.cfg
, pinning mechanize to a very old version, which in return conflicts with the requirement of zope.testbrowser, demanding a higher version of mechanize.While resolving this would be nice (unpinning leads to another error) the question comes up, if zope.testbrowser needs to be involved in a non-testing environment at all?
And even more importantly: Can the configs of dist.plone.org be seen as a reliable source or is it better to use other sources?
version and requirements information containing mechanize: [versions] constraint on mechanize: 0.1.11 Requirement of zope.testbrowser: mechanize>=0.2.0 While: Installing. Getting section instance. Initializing section instance. Installing recipe plone.recipe.zope2instance. Error: The requirement ('mechanize>=0.2.0') is not allowed by your [versions] constraint (0.1.11)