无法在 Plone 中更新 zope.schema
设置 Plone 4 并尝试集成 Solgema.fullcalendar 非常新，但在运行 buildout 时，我收到一条错误消息，说它需要 zope.schema 3.6.0，而我有 3.5.4。我一生都无法弄清楚如何更新它。我认为我在这里遗漏了一些基本的东西，但正如我想象的那样，它正在影响我的头脑，因为随着我的进步，我会一次又一次地遇到此类问题。
“正在安装实例。 错误：存在版本冲突。 我们已经有：zope.schema 3.5.4 但 z3c.form 2.4.2 需要 'zope.schema>=3.6.0'。”
环顾四周，注意到将 zope.schema>=3.6.0 放入 Egg 中可能会起作用，但这实际上并没有触发更新，只是导致了错误的安装错误。
如果有人有任何想法或需要更多内容，请告诉我，
谢谢 ！ 克里斯
Very new to setting up Plone 4 and trying to integrate Solgema.fullcalendar but when running buildout I get an error saying it needs zope.schema 3.6.0 and I have 3.5.4. I cannot for the life of me work out how to update it. I assume I am missing something fundamental here but it is doing my head in as I imagine as I will encounter this kind of issue again and again as I progress.
" Installing instance.
Error: There is a version conflict.
We already have: zope.schema 3.5.4
but z3c.form 2.4.2 requires 'zope.schema>=3.6.0'."
Looked around and noticed that putting zope.schema>=3.6.0 in eggs might work but that didn't actually trigger an update just caused a bad install error.
If anyone has any ideas or needs something more to go on please let me know!
Thanks
Chris
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果您想在 Plone 中使用 z3c.form，最好更新到 Plone 4.1，该版本目前可作为候选版本。 4.1 附带了 z3c.form，并且有更新的 zope.schema 版本。
在一般情况下，您需要在构建配置中有一个版本部分，您可以在其中为您想要的所有发行版指定确切的版本要求。
在 setup.py 文件中，您永远不应该指定确切的版本要求。仅当您的特定库绝对需要另一个库的新功能时，才对这些提出最低要求。
If you want to use z3c.form inside Plone, best update to Plone 4.1 which is currently available as a release candidate. 4.1 comes with z3c.form in it and has the newer zope.schema version.
In the general case you will need to have a versions section in your buildout configuration in which you can specify exact version requirements for all distributions you want.
Inside the setup.py files you should never specify exact version requirements. Only put minimum requirements into these if your specific library absolutely requires a new feature from another library.
参见汉诺的回答。我要补充的是，我想不出一个好的理由来使用“>=”（或“<=”或“==”）在构建配置中的任何位置指定最小、最大或精确版本。版本规范应仅位于 [versions] 部分中。自从我上次使用使用比较运算符的构建配置以来已经有一段时间了，但我记得它可能会导致问题，尤其是在升级时；有时，唯一的出路是删除“.installed.cfg”文件以使 bin/buildout 以全新状态运行。
（请注意，setup.py 中的 '>=' 完全没问题。）
See Hanno's answer. I will add that I cannot think of a good reason anymore to use '>=' (or '<=' or '==') to specify minimum, maximum or exact versions anywhere in a buildout config. Version specifications should only be in a [versions] section. It has been a while since I last used a buildout config that used the comparison operators, but I remember it could lead to problems, especially when upgrading; the only way out would at times be to remove the '.installed.cfg' file to make bin/buildout run in a fresh state.
(Note that '>=' in a setup.py is perfectly fine.)